New Whitepaper: A User Story Primer

In an earlier  post, I announce my latest book project, Agile Requirements: Lean Requirements Practices for Teams, Programs and the Enterprise, and noted that I’d be sending out snippets for review (and hopefully use by others) during the project. Of course, you can’t write about agile requirements without writing about user stories, and although I’ve [...]

Announcing an Upcoming Book on Agile Requirements

As readers of this blog know, I’ve been using my previous book, Scaling Software Agility: Best Practices for Large Enterprises, as a source reference to help guide large-scale enterprises in becoming more agile in their software development projects. In the course of many engagements with these large enterprises, a recurring theme keeps popping up, “How [...]

Lean and Scalable Requirements Information Model Published at Modern Analyst

The latest version of the Lean and Scalable Requirements Information Model for the Agile Enterprise is now published in the July ejournal of the ModernAnalyst.com. For those of you interested in trends in requirements practices, this is a good source for all things requirements and business analyst related, agile or not.
With respect to agile development, [...]

Presentation: Lean and Scalable Requirements Model for Agile Enterprises

I just posted this presentation, my keynote for the 2009 Lean&Kanban conference,  on the resource page. For more on the topic, see the whitepaper (also on the resource page) or the requirements category on this blog.

Reviewers Comments on the Lean and Scalable Requirements Information Model

Mauricio Zamora, my collaborator on a number of other projects, recently took the time to do a thorough review and critique of the new whitepaper A Lean and Scalable Requirements Information Model for the Agile Enterprise (available on the resource page). He raised a number of supportive, as well as differing points of view. I [...]

New Whitepaper: A Lean and Scalable Requirements Information Model for Agile Enterprises

For any who have been following the requirements blog series and category, my collaborator, Juha-Markus Aalto and I have just completed a whitepaper which integrates the lean and scalable requirements information model with the Big Picture Series in a narrative format. It’s not quite as deep as the blog series and some content (like Use [...]

Use Cases in the Agile Enterprise Requirements Information Model

Note: this is the conclusion (for the moment at least) of an extended series on a Lean and Scalable Agile Enterprise Requirements Information Model, which can be found in the Agile Requirements blog category.
In an earlier post “What, No Use Cases in the Requirement Information Model?”, I noted the following.
“Regarding use cases, I haven’t yet [...]

Agile Requirements Information Model: More on Non-Functional Requirements (System Qualities?)

Note: This is part of a series on a Lean and Scalable Agile Enterprise Requirements Information Model. Refer to that series for additional context.
In an earlier post, Agile Requirements Information Model (5) – For Agile Programs (b): Nonfunctional Requirements, we introduced Non-Functional Requirements as “Backlog Constraints” and highlighted the important role these types of requirements play [...]

Updated Agile Requirements Information Model

For those of you following the Agile Requirements series, you will have already noted that the model has been changed and extended over the course of the series. For reference purposes, the updated “basic” information model is below:
As the series has progressed, the model has been further elaborated with additional subtypes and a few new [...]

What, No Use Cases in the Lean and Scalable Agile Requirements Model?

Just the other day, I received the comments below (read the excerpt below the dashed lines) from Jennifer Fawcett, of www.agileproductpowner.com. Jennifer worked with me at Rational and Proquo (as an extremely capable agile product owner) so we have a long history together.
In her comments, Jennifer asked why there was no mention of use cases [...]