1 day workshop in requirements development using “Product Based Planning” for software solutions.
Participants will leave this workshop with a common understanding and structure to work effectively with requirements development and management. Following lean principles you will learn the process by which the team can incrementally build requirements that add value. We will use the concept of product based planning.
Product based planning enables us to start with a vision of the end product in mind.
By having a vision (blueprint) of the end product we can visualise the component products required to make up the end product. Once we have this visualisation we can then start development of the product, putting together component products and sub-component products in the order that gives us most value. This is a bit like the 20/80 rule, first build the 20% that will give us 80% of the value.
By progressively developing the product or service and possibly releasing to the market we can get feedback from the market or internally regarding the suitability of the product(s) being developed. Based on the lessons learned the project team can make controlled changes to the product or service requirements to ensure that business objectives are met.
When documenting requirements the emphasis is on relevant documentation and keeping the documentation to the minimum necessary to effectively deliver the final product or service. The level of documentation will be dependent on the stakeholders, industry and legal requirements.
For longer term projects the development of detailed requirements can be deferred until later in the project, this will result in more relevant and better quality products/services delivered at lower cost.
Client companies / departments
• Department managers and senior managers who are responsible for ordering products or additional features from internal or external suppliers.
• Personnel who have to work with the product once it is delivered should be involved in the development of the “User Scenarios and Acceptance Tests”
• Project managers / product owners
Companies / departments supplying solutions
• Project managers and sales personnel should attend this course so that they are able to manage the clients’ expectations in a professional manner and to understand what is involved in the process of developing requirements and why it is important.
• Technical team leads/managers
Course Introduction (09:00 – 09:15)
• Benefits related to using “Product Based Planning” when developing requirements.
Period 1 (09:15 – 10:30)
• SO 1: Develop the Project Product Description
• SO 2: Develop Product Breakdown Structure
Period 2 (10:45 – 12:00)
• SO 3: Develop Component Product Descriptions
• SO 4: Develop Product Flow Diagram
Updating the product breakdown tructure and project product description
Period 3 (13:00 – 14:30) & 4 (14:45 – 16:00)
• SO 5: Develop User Scenarios and Acceptance Tests for Individual Products.
The process guide and templates will enable participants to apply their knowledge directly upon returning to work.
(Please note that templates are supplied in the word 2010 format.)
1. Requirements Development Process Guide
2. Project Product Description Template
3. Component Product Description Template
4. User Scenario & Acceptance Test Template