Scrum is a flexible agile development practice / method / framework built around some agile principles and on top of BDD. Scrum is one of many agile methods. Each SCRUM team is recommended to be not too big. In Scrum practice, features of products are written from the perspectives of end users. Features are known as user stories. The collection of user stories are called product backlog, which is a wish list to make end product great.
A SCRUM team is cross-functional, typically 7 people plus or minus 2, no more than 9.
Share thoughts and concerns to understand the workflow.
A fast-pace standup meeting list the work, obstacle, solutions since the last meeting to keep the team in sync.
Sprint Planning Meeting
A meeting at the beginning of a sprint in which the Product Owner and the team negotiate which stories a team will tackle. To plan a release,
1. Start with product backlog to identify what user stories to put into a Release Backlog.
2. The team then estimate stories and Product Owner have user stories ordered in the Release Backlog to come up with a total amount of work to complete the release. To estimate user story, one approach is to adopt story points, another approach is to estimate in 1,2,4,8 hours, 2,3,5,10 days, 1,2,3,6 months. Estimate in between will fall into the next larger bucket.
3. Lastly, plan out several Sprints (2-12) for a given release. At the end of each sprint, have a Sprint Retrospective meeting to reflect and improve.
Sprint Review Meeting
At the end of a sprint, the team presents their work to the product owner who either accepts or rejects the work.
Sprint Retrospective Meeting
A meeting held at the end of each sprint to reflect and improve.
Possible drawbacks of adopting SCRUM are similar to those reasons why many developers have taken up side-projects that do not even offer up a paycheck. These drawbacks are: