The maturity model approach to describing organizations and processes comes and goes out of fashion. It is a repeating framework de jour. In the game of agile jargon whack-a-mole, the agile maturity model is poking its head up again.
Agile / Ishikawa Diagram / Product Management / Requirements / Requirements Models / Software development / Testing
Posted on:
Failure To Launch (Your Product)
Jump forward in time to the day of your next big product launch (first release, new features, new market segment, etc). And your site/application crashes due to the “unexpected” demand. All you can do now is look for a bucket of water to put out the fire. What could you […]
Agile / Business Analysis / Product Management / Requirements / Requirements Models / Software development / User Stories
Posted on:
Agile Non-Functional Requirements
Just because your requirement is not a user story does not mean you have to throw it out when planning your next sprint. See one way (that is working) for managing non-functional requirements with an agile team.
Agile / Business Analysis / Product Management / Requirements / Requirements Models / Software development / User Stories
Posted on:
User Stories and Use Cases
User Stories are one of the key agile artifacts for helping implementation teams deliver the most important capabilities first. They differ from use cases in some important ways, but share more commonalities than you might think.
Agile / Communication / Product Management / Project Management / Requirements / Requirements gathering / Software development
Posted on:
Stakeholders in a Barrel
There’s really only one way to travel down a waterfall – in a barrel. A lot of people died this way, but some survived. Software projects have been predominantly waterfall projects since the start of software projects. And stakeholders rode down those projects, basically in a barrel. The people riding […]
Agile / Product Management / Software development
Posted on:
ProductCamp Austin Winter 2009
The second productcamp for Austin is just around the corner! Are you going to be there? You should.
Agile / Business Analysis / Business Rules / Communication / Consulting / Product Management / Software development
Posted on:
Simple Agile Model Example
A picture is worth a thousand words. Agile values working software over comprehensive documentation, and it values customer collaboration over contract negotiation. With that in mind, how much is a picture of a model worth? Check out a simple example, how it helped, and what we didn’t do.
Agile / Product Management / Requirements / Software development
Posted on:
Satisficing Sprints
Satisficing probably makes more sense than perfecting your product. Can? Open. Worms? Everywhere. Are we really saying “don’t make it perfect?” Yup.
Agile / Prioritization / Product Management / Requirements / ROI / Software development
Posted on:
Plan Your Next Sprint By Bang For The Buck: Part 2
Planning by ROI. Hmmm. Isn’t that impractical? In an econometric way, yes. But you can still estimate the relative value of the capabilities / stories you’re planning for your scrum sprints. The point is – don’t look only at value – also look at costs. While “ROI” may be a […]