For an agile project to progress smoothly, the backlog must be groomed and ready for each sprint. That work must be included in your project plan. This article gives you five points to consider when planning that work.
Agilists value working software over comprehensive documentation. But writing requirements remains an indispensable process that should occur throughout the life of your projects. Here are six great reasons, spanning discovery to delivery, for why we value requirements and user stories.
When project teams are buried in the details of their work, it’s easy for them to forget that they are producing solutions for real people. PMs need to help them remember.
We’ve all had projects that experienced bumps in the road. If you find yourself with major challenges, there are six key questions and actions to consider to make sure you’ve covered all of your bases.
Poor request management will get your project off to a bad start from which it may never recover. Here are four recurring request management issues that derail project, program and portfolio effectiveness, from the gathering to prioritizing and tracking of them. How many sound familiar?
What are the characteristics of a good requirement? What differentiates it from a bad one? Generally, in order for a requirement to be good, it must meet four basic criteria. Do you have what it takes?
Project leaders rush or minimize the requirements management process at their own peril. However, if we spend too much time on requirements, we are at risk of creating a burdensome process that will delay the project. It is important, then, to apply the appropriate amount of requirements rigor to our projects.
It is not uncommon to hear deadline-stressed project managers and team members rationalize about why requirements management is not necessary. But short-changing business analysis activities is one of the leading causes of rework and delays.
In part three of our series, here is an overview of the key planning activities, sub-processes and deliverables involved in requirements planning, which should be driven by the business analyst as a member of the project team.