Loading...
 

Outcomes-Requirement-Workshop

Plugin execution pending approval

This plugin was recently added or modified. Until an editor of the site validates the parameters, execution will not be possible.


One reason for failure in projects, including well executed agile projects, is the failure to capture, define, communicate, develop and deliver the outcome that defines success. The other side of this is that we have a growing number of people and projects that have mastered these skills, and they seem to be out-performing their competitors hands down. In this workshop you will learn how to capture, define, communicate the outcomes that defines success, in a clear, quantified, structured way; so it can be developed and delivered.

Training Content

Projects are funded so as to create value to a set of Stakeholders. We can call those values for business and Stakeholder values. 

For IT projects, those values are normally created by delivering products with Functions that Work well for the users, helping the users do what they need to do. We can call those Product Values. Examples of Product Values are usability, performance, security, adaptability, robustness, expandability, reliability and there are many more. Functions and values don’t explain how they are created, but rather how well the Product does what it does. We can call these the outcomes we want to get out of the project. The business, Stakeholder and Product Value (outcomes) defines project success 

In this workshop you learn how to:

  1. separate the outcomes from the designs/solutions/architecture.

  2. classify the outcomes into useful types

  3. place the outcomes into its correct Level (business, Stakeholder, Product, sub-product, Solution -level)

  4. write each outcome Type in a way that is best suited for that Type. A technical Solution, a Function and a Product Value needs to be handled completely differently.

  5. write pure Functions without design or value.

  6. write the Product Values so they accurately represent the outcome values the users, project sponsors and the other Stakeholders hold as success.

  7. write the Product Values so they they are useful for Product owners, engineers and architects to prioritize so as to create success.

  8. write the Product Values so the developers can develop towards them and testers can test them.

  9. write the Product Values so they can be delivered to appropriate users.

 

Who is the training for

If you are concerned with achieving project success, it’s for you!  
If you are a product-owner, it’s for you! 
If you are outsourcing, it’s for you! 
If you write Requirements. it’s for you!
If you are a business analyst, it's for you!
If you call yourself an architect, it’s for you!
If you design the Product, it’s for you! 
If you prioritize, it’s for you! 
If you want to deliver value to your Stakeholders, it’s for you!

If you are still reading this text, it’s for you! 

or not?

If you think user-stories are sufficient, and like to keep that illusion, it’s not for you!
If you don’t really care about project success, it’s not for you!
If you just want to code, it’s not for you!
If you think agile is the Goal, not a potential Solution, and like to keep that illusion, it’s not for you!
If you don’t like to think critically, it’s not for you!

Is this for you? you decide! If yes, please sign up!   

Certification

Image
You will acquire a Value Requirement - Trained certification.
For more information, see: Value+Requirements+Certification
For a list of certificate holders, see: www.ValueCertification.com 


 

Created by system. Last Modification: Thursday 22 of May, 2014 14:36:12 CEST by Kai Thomas Gilb.