My trainer taught us 2 important point about Scrum : Requirement and Estimate. For the first time I have attracted by SCRUM, a little funny that I studied about SCRUM in a course of an IT company and this company gave me a certification about SCRUM but what I have learned was just theory, oh I must hang this certification paper on wall - in a solemn position.
1. A visual requirements gathering for the product backlog:
 |
| Simple product backlog |
1.1. Identify the Stakeholders and their goals :
The best goals follow these properties:
 |
| These properties almost are the same with above list! ( an interesting thing I just explore!! hehe) |
> Specific : Everyone will have the same understanding as to what the goals are.
For example : In my company, everyone has an English name beside their Vietnamese name. When I introduce my E name to people, I said " hello everyone, my name is Hila", I want people to have the specific understanding about my name, Hila means a gorgerous and funny girl who is always happy. If anyone think Hila means the plural form of Hilum :
I'm so sad :) hehe.
> Measurable : We can objectively determined if the goals have been reached.
> Achievable : The stakeholders agree as to what the goal are.
> Realistic : We shall be able to achieve the goals for the project with resource we have.
> Time-based : We will be given enough time to achieve the goals.
1.2. Gathering the requirement for the product backlog
Forest => Tree (Overall product, ask yourself what your new product should be composed of => Braches => Leaves (Stories)
>Consistent: A consistent requirement does not conflict with another requirement.
>Unambiguous
: The reviewers of a requirement statement should be able to draw only one
interpretation of it, regardless of their role.
>Testable:
We should be able to create test cases for a requirement. If a requirement is
not testable,
trying to determine whether it is correctly implemented is a matter of opinion.
>Feasible: It must be possible to implement each requirement within the known capabilities and limitations of the system environment
>Independent: No user story (PBI) should be dependent on another user story (PBI).
>Traceable: You should be able to link each requirement to a user and to his goals.
AN EXAMPLE :
>Feasible: It must be possible to implement each requirement within the known capabilities and limitations of the system environment
>Independent: No user story (PBI) should be dependent on another user story (PBI).
>Traceable: You should be able to link each requirement to a user and to his goals.
AN EXAMPLE :
 | |
| Room reservation software product and its tree |
 | ||
| User management tree and its branches |
 |
| The trees and forest approach applied to software product development |
