The CEO of the company hired a Scrum Master to help the team to learn agile development and follow a Scrum process to develop a product.
The Scrum process
The Scrum process starts with the Product goal the team has to deliver.
Scrum Master first meets with the Product Owner to understand the vision and goals.
The Product Owner spent the last few months speaking to customers about the project.
Product Owner suggests building a mobile application.
User Stories
1. Scrum master talks to the Product Owner to break down the problem into a set of user stories.
2. User Stories are central to agile development because they explain what users want and why this keeps the user out of specific technology decisions and ensures that developers don't blindly follow specs that don't really describe the goal.
3. Each User story should describe-
- What specific problem you are solving.
- Why it is important to the user and the overall product.
- Any implementation limits.
4. The Product Owner documents each user's stories and places them in a queue called a Backlog.
5. When the Developers meet in the Scrum meeting for the product. They can commit to how many user stories they believe they can get done in a sprint. (For the company sprint is two weeks long.) In the Scrum meeting, The team has the final say on how much work can be done in a sprint, Each developer commits to his/her part of the sprint.
Stand-up Meeting
1. During the project the Developer team meets every day for what's called a Stand-up Meeting.
2. Each Developer identifies issues that are blocking his or her work as well as describes the current status. The goal of the meeting is to ensure everyone is on the same page and to identify as early as possible. Any issue that could delay work or require a change in plan.
3. The Scrum Master's role is to serve the team to enable their productivity and maximize their success in hitting their commitments.
4. Here Scrum Master handles the Blocking issues with the Engineering team so that Developers can make their commitment.
Review Process
1. The sprint concludes and the review begins.
2. The Scrum master gets feedback from everyone. So everyone is able to speak on improving the process.
Strategic Practices
1. With the team succeeding from sprint to sprint the scrum master begins working on strategic practices.
2. Scrum Master develops a planning process to help fill the backlog and develop a product roadmap with the Product Owner.
3. Scrum Master also works with the operation team on an application release process. So the development team pushes out frequent improvements to the application.
Happy Customer
With frequent product improvements based on the feedback Customer are happy.
The Scrum Master, The person who makes the process smooth to get a happy result.