As a software development blogger, I often write about ways for teams to adopt agile practices or be more agile. There is no single way to be agile. There are many. There is no best way to be agile. There are multiple. What can your team do? Ultimately, software development teams must establish rules and […]
This is the seventh in a series of posts that began with “How to Capture Software Requirements Using Story Roadmaps”. The focus of this final post is the user stories. If you’ve been following this series since the beginning, you already know how to write good user stories. The INVEST model coupled with the standard […]
This is the sixth in a series of posts that began with “How to Capture Software Requirements Using Story Roadmaps”. It started with goals and will end with stories. The focus of this post is epics. If your software development team has gotten this far along on the User Story Roadmap, the epics should be […]
This is the fifth in a series of posts that began with “How to Capture Software Requirements Using Story Roadmaps”. The focus of this post is themes. Agile software development projects usually rely on user stories as the primary vehicle for capturing software requirements. Yet, user stories are often criticized for being disjointed and confusing. […]
This is the fourth in a series of posts that began with “How to Capture Software Requirements Using Story Roadmaps”. The focus of this post is stakeholder needs. Now that you know the goals of the project and who really cares about reaching them, it’s time to consider needs. Every stakeholder has needs. If the […]
This is the third in a series of posts that began with “How to Capture Software Requirements Using Story Roadmaps”. The focus of this post is stakeholders. The importance of stakeholders in any enterprise software project cannot be overstated. Let me say that again … The importance of stakeholders in any enterprise software project cannot […]
This is the second in a series of posts that began with “How to Capture Software Requirements Using Story Roadmaps”. The focus of this post is business goals. Every project needs a goal or a set of goals. These are high-level descriptions of the context for the project and the business value to be delivered. […]
There’s much disagreement among software practitioners about how to capture requirements. Some argue in favor of lengthy, detailed documentation. With equal vigor, others argue in favor of simple tools like user stories. What should you do? There are valid arguments on both sides. Detailed requirements documentation can supply levels of insight that are hard to […]