Immersion Reporting: The Requirements Alternative
byIf traditional data-gathering techniques aren't providing the information necessary to create solid requirements, consider another option not often used by project teams.
If traditional data-gathering techniques aren't providing the information necessary to create solid requirements, consider another option not often used by project teams.
It is through gaining a better understanding of the uncertainties—and better managing them in relationship to the project environment and stakeholders involved—that PMs may more effectively approach and complete their endeavors to contribute more value.
The term “PMO” means different things to different people, leaving room for interpretation. Determining the type of PMO requires a project manager to be a strategic thinker possessing technical project and business management expertise.
Why do stakeholders' eyes roll when you try to explain why earned value is a good thing--and how it works? Ever wonder why claiming partial credit for projects in progress is met with skepticism and ire? Maybe it’s time to rethink the concept of EV as a way to measure project performance and progress.
Many project teams shy away from incorporating use cases into their Agile approaches because they resemble the non-Agile techniques of elicitation and analysis. But there are golden opportunities to leverage the power of use cases with user stories when developing Agile requirements. Let’s look at when and how.
When we see the same view every day, we get complacent. A prudent project manager does not rely on any single view of the project, as multiple views can expose unforeseen problems and opportunities.
The most basic form of requirement in an Agile project is the User Story. It describes an actor, what the actor is trying to do, and the actor’s goals. Each story is unique, but they all should have the same components and adhere to the same guidelines. To make this happen, consider the acronym INVEST.
It was the best of times--your project seemed to be going along swimmingly. It was the worst of times--suddenly there was a surprise from a governance stakeholder. Will you avoid the guillotine?
Your project seemed to be going along swimmingly. Suddenly, there was a surprise from a governance stakeholder. Will you avoid the guillotine? In our conclusion, we focus on managing governance stakeholders in requirements gathering.
Have you noticed that as project execution approaches evolve, they become more Agile (or at least “small ‘a’ agile”)? Does that create opportunities for more formal acceptance of agile concepts throughout organizations?