Scrum

Filter

Categories
Standards
Products
format
  1. voucher (3)
  2. eBook (3)
  3. hardcopy (3)
  4. ePub (1)
Language
  1. german (1)
  2. dutch (1)
  3. english (1)
  4. japanese (0)
  5. italian (0)
  6. korean (0)
  7. portuguese (0)
  8. russian (0)
  9. polish (0)
  10. french (0)
  11. arabic (0)
  12. turkish (0)
  13. swedish (0)
  14. brazilian portuguese (0)
  15. chinese (0)
  16. finnish (0)
  17. danish (0)
  18. spanish (0)

Scrum

Grid List

Set Ascending Direction

Scrum

1 Title/current version of Scrum books
Scrum books

2 The basics of Scrum books
Scrum is an iterative, incremental framework for project
management often deployed in Agile software development.

3 Scrum books summary
Scrum is an Agile method (an iterative and incremental
approach) for completing complex projects. Scrum was originally
formalized for software development projects, but works well for
any complex, innovative scope of work.

Why is it called Scrum?
When Jeff Sutherland created the scrum process in 1993, he borrowed
the term ‘scrum’ from an analogy put forth in a 1986 study by Takeuchi and
Nonaka, published in the Harvard Business Review. In that study, Takeuchi
and Nonaka compare high-performing, cross-functional teams to the scrum
formation used by Rugby teams.
Source: www.Scrumalliance.org

The Scrum Guide is the offi cial Scrum Body of Knowledge. It
was written by Ken Schwaber and Jeff Sutherland, co-creators of
Scrum. The current version is Scrum Guide Version 2013.
The Scrum framework is summarized in the Sprint Cycle
(see Figure).

Scrum Sprint Cycle

A Sprint Cycle consists of the following steps:
− A Product Owner creates a prioritized wish-list called a
Product Backlog.
− During Sprint planning, the team pulls a small chunk from
the top of that wish-list, a Sprint Backlog, and decides how to
implement those pieces.
− The team has a certain amount of time, a Sprint, to complete
its work – usually two to four weeks – but meets each day to
assess its progress (daily Scrum).
− The Sprint Burn Down chart shows implementation progress
during a single Sprint.
− Along the way, the ScrumMaster keeps the team focused on
its goal.
− At the end of the Sprint, the work should be potentially
ready to hand to a customer, put on a store shelf, or show to a
stakeholder.
− The Sprint ends with a Sprint Review and retrospective.
− As the next Sprint begins, the team chooses another chunk of
the Product Backlog and begins working again.

The cycle repeats itself until suffi cient items in the Product
Backlog have been completed, the budget is depleted, or a
deadline arrives. Which of these milestones marks the end of
the work is entirely up to that specifi c project. No matter which
impetus stops work, Scrum ensures that the most valuable work
has been completed when the project ends.

The two main roles in Scrum are the Product Owner, who
represents the customer and manages all requirements (adds
requirements with a detailed description, prioritizes requirements
and plans releases); and the ScrumMaster, who helps the team
to follow Scrum process. The ScrumMaster facilitates the daily
Scrum meetings, manages any problems, supports the Product
Owner, and removes obstacles to team progress.

4 Target audience of Scrum books
Any member of a project team.

5 Scrum books scope and constraints
The scope of Scrum was originally intended for software
development projects, but it is now also used for delivering any
kind of complex projects.

Strengths
• Productivity increases (from 10% to 400% depending on
team, environment, project, Agile experience, etc.)
• Continuous development process improvement
• Communication improvement inside development team and
between Scrum team and customer
• Minimized time-to-market via frequent releases

Constraints
• Requires a lot of preparation/planning
• Focus on supporting tools
• Does not work well if team culture does not allow for roles as
required in a cross functional team

6 Relevant website of Scrum books
www.scrum.org

 

 

Read more