The role of product manager and Scrum
Product manager is the CEO of product.
He or she interprets user requirements into actual roadmap/todo-list of dev team.
Scrum means the development period typically in two weeks. It is highly predictable and productive if everyone agrees with the concept and development plan.
The steps of Scrum
There are 5 steps in the Scrum process.
- Grooming - define everything
- Planning - connect the plan to budget and schedule
- Daily-standup
- Spring Demo
- Review and retro
There are several endless issues in the Scrum process.
- It consumes too much time
- There are countless definitions of value
- lack of agileness
- No accountability and vague responsibilities
Hierarchy, Epic, Stories
To manage the development process, PM and dev team use these terminologies.
- Stories: also called “user stories,” short requirements or requests written from an end user's perspective.
- Epics: large bodies of work that can be broken down into a number of smaller tasks (called stories).
- Initiatives: collections of epics that drive toward a common goal
Stories are higly technical tasks, and epics are similar to minor functions. Then, initiatives represent user benefits.
The vital point is each story has acceptance criteria(required level of completion) and story points(complexity of the task).
Members of dev team need to align with the level of difficulty of each story and 100 % agree with what they are going to do.
