Simplified scrum guide

[Mobile version(QRCode)] Total views:49,910 / Applauds for blog:1
Welcome to my page. I am an adminisrator of this site.
If you are this db's user, please contact with me by private mail. If not, please contact with me by email or twitter or facebook
Access record[Graph / PV Info.(Past 1 day / Past 1 week) / Access from outside (Yesterday / Past 1 week) / Vistors's list]
ProfilePmail(Mail)
Inbox   /Send   /Sent
Reviews(List   /Limit)
Poll   /Agree:Got   /Sent
Fan
Works/Music
Blog
[Write]
Links
My Play List
<=Newer article2016/09/25 List to be studied more
=>Older article2016/08/02 Pipeline

1.
2016/09/21 "Scrum > Simplified scrum guide"
[Show only this article / Modify / Delete / Send trackback / Add to the shared category]

1. Definition of Scrum
2. Scrum pillars (Transparency, Inspection, Adaption)
    1. Transparency
    2. Inspection
    3. Adaptation
3. The Scrum Team and its 3 Roles
    1. The Product Owner
    2. The Development Team
    3. The Scrum Master
4. Scrum Events
    1. Sprint
        1. Sprint Planning
        2. Daily Scrum
        3. Sprint Review
        4. Sprint Retrospective
5. If you want to learn more by yourself
    1. Certificates

1. Definition of Scrum

Original scrum definition document


Scrum is development framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible business value.
In order to make these things visible, Scrum Teams need to frequently inspect the product being developed and how well the team is working.
With frequent inspection, the team can spot when their work deviates outside of acceptable limits and adapt their process or the product under development.
2. Scrum pillars (Transparency, Inspection, Adaption)

In Scrum, decisions are made based on observation and experimentation rather than on detailed upfront planning. Empirical process control relies on the three main ideas of transparency, inspection, and adaptation.
    1. Transparency

Transparency allows all facts of any Scrum process to be observed by anyone.
    2. Inspection

Scrum users must frequently inspect Scrum artifacts and progress toward a Sprint Goal to detect undesirable variances. Their inspection should not be so frequent that inspection gets in the way of the work.
    3. Adaptation

Adapt based on inspection quickly
3. The Scrum Team and its 3 Roles


    1. The Product Owner

The Product Owner is the sole person responsible for managing the Product Backlog.
    2. The Development Team

The Development Team consists of professionals who do the work of delivering a potentially releasable Increment of Done product at the end of each Sprint.
Only members of the Development Team create the Increment.
    3. The Scrum Master

The Scrum Master is responsible for ensuring Scrum is understood and enacted.
Scrum Master Service to the Development Team.
4. Scrum Events

These events are specifically designed to enable critical transparency and inspection. Failure to include any of these events results in reduced transparency and is a lost opportunity to inspect and adapt.
    1. Sprint

The heart of Scrum is a Sprint, a time-box of one month or less during which a Done, useable, and potentially releasable product Increment is created.
Sprints best have consistent durations throughout a development effort (duration should be 1 week - 1 month).
A new Sprint starts immediately after the conclusion of the previous Sprint.
      1. Sprint Planning

Maximum duration: 8 hours for 1 month sprint (4 hours for 2 weeks sprint / 2 hours for 1 week sprint)
Outcome:
- Sprint backlog: What can be done this Sprint?
- Story points for sprint backlog: How will the chosen work get done? How much time will be expcted for them?
- Sprint Goal: What will we achieve in this sprint?
      2. Daily Scrum

Maximum duration: 15 minutes per day
Outcome:
- What did I do yesterday that helped the Development Team meet the Sprint Goal?
- What will I do today to help the Development Team meet the Sprint Goal?
- Do I see any impediment that prevents me or the Development Team from meeting the Sprint Goal?
      3. Sprint Review

Maximum duration: 4 hours for 1 month sprint (2 hours for 2 weeks sprint / 1 hours for 1 week sprint)
Outcome:
- Demonstration by dev team
- Revised Product Backlog that defines the probable Product Backlog items for the next Sprint
      4. Sprint Retrospective

Maximum duration: 3 hours for 1 month sprint (1.5 hours for 2 weeks sprint / 45 minutes for 1 week sprint)
Outcome:
- List up what was done well and what was done bad
- List up how to improve what was done bad as todo list
- Move what was done well as keep items

The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint.
5. If you want to learn more by yourself

First of all, you should read original definition document again and again considering your actual work. And aiming to get certificate will help you to have solid and proper knowledge of scrum.
    1. Certificates

Representative certificates
PSM (Professional Scrum Master Assesments)Exam base certificate
Certified Scrum MasterAttendance base certificate
PSM is good as certificate because it will force you to study and criteria is high (85%).
After at least you succeed in passing Open assessment, you can try PSM I and if you pass, you can get the following certificate and your name becomes searchable as a holder.


Add comment to this article


[Read other articles]
<=Newer article2016/09/25 List to be studied more
=>Older article2016/08/02 Pipeline


Articles categorized as "Scrum by this user"
All articles of this user
Subscribe to RSS
RSS
Display Style of blog
List/Mobile(QRCode)
Term
Category
All
1.Japan
2.Atlassian's products
3.Self
4.Development of this site
5.Japanese comics
6.Japanese anime
7.Weekly hot news of Japanese culture
8.OP/ED/PV
9.Japanese game
10.Ranking
11.Japanese Comics (Manga)
12.Search Engine
13.Japanese drama
14.Japanese otaku culture
15.Programming
16.Ineternet world
17.Movie
18.C/C++
19.BerkeleyDB
20.Apache programming
21.Spam
22.Meteor
23.Marketing
24.Python
25.Scrum
26.JIRA
27.Git
28.CI
29.Jenkins
30.AWS
31.Operation
32.Singapore
33.Cloud
34.Mysql Cluster
35.DevOps
36.Bitbucket
37.Xamarin
38.Good and new
39.Monitoring
40.node.js
Sayings from S-Cry-Ed

Rule in this world is speed. Even stupid person can write cool novel if he can spend 20 years for it.

If someone helped me, I will help him in return, which is my rule.

To become stronger, consider what is cowardliest thinking. And rebel against the thinking, which will make you stronger.



I am Japanese but working for some English sites.

Doctor Job Career
Nurse Job Career
Top Page top MetaSeachJP Works