Need some help digesting earned value management? An EVM project that is “broken” before its completion is easier to reconstruct and make useful...so open wide and get ready to chew.
310 items found
One of the most established standards organizations (and their pronouncements) is often missing from the IT governance conversation: the International Organization for Standardization. Did you know that the ISO has been very active in the governance and compliance space? Here is an update on the standards that you might find useful.
How can companies foster collaboration between business analysts and quality assurance professionals? New research recommends three steps to strengthen alignment between these complementary roles — and improve project outcomes.
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.
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.
Customer (or user) satisfaction is fundamental to a project’s success. Understanding and documenting customer attitudes and needs will better prepare project teams to meet expectations and deliver the anticipated benefits. It starts with the requirements gathering phase.
Bringing the customer into the requirements process is a key to success in every project. Sometimes, however, their expectations are unrealistic or even contrary to their best interests. Along with good facilitation, there are ways to negotiate with customers that give them the option to say "no" without you having to insist on it.
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.
When gathering requirements, many participants will be eager to dive into very specific user needs. But what is the right level of detail when it comes to business requirements? What are the risks of too much or too little information?
What makes a requirement a good requirement? Good requirements generally meet four basic criteria: they address a specific need; they are verifiable; they are attainable; and they are clear.