What SCRUM framework looks like ?

Different from waterfall, SCRUM is put emphasis on creating a viable product in a short term and getting the feedback from users in order to modify immediately, make sure the producing is going on the right way. Let’s take a look at how SCRUM works.

1. Team up

The proper number of people in a group is about 5 to 9 people, and there are 3 key charaters including:

a. SCRUM Master — A person who is responsible for leading the team to make good use of SCRUM, helping to make communication work between team members, and drive the process to the correct direction.

b. Product Owner— A person who knows every member very well (particuler profession, skill…etc.) and is in charge of defining, adding, deleting, modifying task list.

c. Team member — people who have open mind and are willing to know about progress from other team members,beside their own profession.

2. Create Task List

Few steps that you can have ideas to make list:

Step1: Put yourself in user’s shoes and have empathy with user story. Define WHY we design this product.

Step2: According to definition of WHY, we have to figure out WHAT functions we will design for product, so we make several tasks and stick on To Do list board.

Step3: Discuss the resource input, the level of correlation to final product, and finalize the priority of tasks by raising hands and pointing out the priority number from team members.

3. Sprint Schedule

With the view of creating a viable product, we need to set up the works that can be completed from task list. Timeline would better be 2 weeks to one month.

4. Sprint

Set up the daily SCRUM meeting for 15 minutes and order the task list to 3 sections: To Do, Onging, Done.

Each member have to describe what has been done yesterday, schedule to do today, and any barrier should be excluded. Purpose of this part is to let team members know the progress from others, timely give a hand when team confront the issues.

5. Review

When the first level of Sprint is finished, we will need the stakeholder’s ( client, supervisor, cross functional teams…) feedback and suggestion about product modification and new requirement that will be banchmark to our task list.

6. Retrospective

Look back to the process of sprint stage and inspect the work flow to pose improvement that can make good effort to the way you work, at the same time to get ready for the next Sprint.

The cores of SCRUM is to let everyone in the team know the progress, daily check, and find the issues then adjust right away.

Want to yield twice the result with half the effort ? Try SCRUM.

If you would like to read more about my writings, please give me 1~5 claps or more, because your encourgement is my motivation!