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 / Prioritization / Product Management / Requirements / ROI / Software development
Posted on:
Plan Your Next Sprint By ROI: Part 1
You’ve got a giant backlog of user stories and product capabilities. How do you determine which stories to implement right now? By the estimated value of each story? Pick the ones the developers want to build next? How about picking the stories that maximize the ROI of the sprint? To […]
Business Analysis / Requirements / Requirements gathering
Posted on:
C.R.A.C.K. Users Are Addictive
Barry Boehm, inventor of the spiral model of software development, may also be the originator of the CRACK acronym for the type of users we want on our projects. When defining (and executing on) projects, we don’t just want CRACK users, we want CRACK stakeholders. And we want them to […]
Business Analysis / Prioritization / Requirements
Posted on:
Stakeholder Value-Delivery Matrix
Roger Burlton, of the Process Renewal Group, gave an excellent presentation Monday morning at the 10th annual International Business Rules Group: Developing a Business Process Architecture and Program of Change. A lot of good stuff about how to define, develop, and manage processes. One idea in his presentation was particularly […]
Business Analysis / Interaction design / Product Management / Requirements / Software development / UX
Posted on:
Managing Stakeholder Goals
A couple weeks ago we wrote about Outside-in Software Development, by Carl Kessler and John Sweitzer. One of their ideas about stakeholders and goals has got us thinking about traceability.
Business Analysis / Requirements
Posted on:
Why Requirements Approval Matters and How To Make It Easier
Getting requirements documents approved can be a pain in the butt. Why do we need to do it in the first place? The approval process is more than just reaching concensus or creating a contract. Done correctly, it presents an opportunity to get more inputs from stakeholders.