We’ve just pushed three new detail pages: Spikes, Tasks and Scrum/Agile Master. (Thanks to Colin for the extra push on these three.)
FYI, all icons on the Framework already have abstracts, so it useable and navigable. We are in the process of filling in the detail pages bottom up, starting primarily with the Team Level. That will take us until about summer. (see the Roadmap).
Also, in case you missed it, we now have subscribe to this blog page (see right column) where we will post updates.
31
MAR
MAR
BLOG
Great work so far! Just quick question, so when do NFRs get done? Should an NFR become a backlog item (like a Story) in an iteration that Agile Team should tasked out? Also, how do we handle compliance type items, like an NFR?
NFRs are a complicated question. We’ve modeled them as “constraints on the backlog” (both Team and Program; see the little NFR icon that anchors the backlog) rather than backlog items, as backlog items can be safely deleted when completed (subject to the persistence of acceptance tests which guard against regression problems). NFRS are usually here to stay and have to be reconsidered for much new functionality. It is an important topic and I devote an entire chapter to them in Agile Software requirements.