Getting Predictable Definition

When it comes to requirements, most of us agree there’s usually ambiguity and confusion. People may think they hear things. They may understand something differently than a colleague. Business stakeholders may change their minds or misunderstand the consequences of a particular decision. It’s not unusual for the project’s business case to get lost -- especially when you have six to 12 month projects and 50+ people making decisions that are not aligned to a common vision.

Getting Predictable Definition solves this problem by creating alignment between IT and the business as well as between business stakeholders. Why is this so important? Because when all the business stakeholders agree to exactly what they need, it makes it easier for the development team to deliver it!

Getting Predictable is a collection of simple, effective best practices that emphasize the value of a shared vision on project success between stakeholders across the organization. Because requirements are defined in terms of business goals, Getting Predictable provides metrics that quantify success in terms that make sense to all project stakeholders. Plus, any ambiguity as to when a project is done, done, done is completely gone, gone, gone.