Site Loader

Typically consists of a team of 7 people who work together in short, sustainable bursts of activity called sprints, with plenty of time for review and. One of the best books I’ve found on the scrum topic is Scrum: A Breathtakingly Brief and Agile Introduction it’s a short, concise book that explains the basics of. Scrum – A breathtakingly brief and agile introduction. (Productivity and Books).

Author: Maulkis Arashitilar
Country: Eritrea
Language: English (Spanish)
Genre: Medical
Published (Last): 12 March 2009
Pages: 375
PDF File Size: 20.14 Mb
ePub File Size: 19.66 Mb
ISBN: 613-5-71440-573-8
Downloads: 80156
Price: Free* [*Free Regsitration Required]
Uploader: Dozahn

While the sprint review is the public end of the sprint, the team has one more meeting: Visit our Beautiful Books page inttroduction find lovely books for kids, photography lovers and more. Experience is the best teacher, and the scrum cycle is designed to provide you with multiple opportunities to receive feedback—from customers, from the team, from the market—and to learn from it.

Then the team members decide if they can commit to delivering that story by the end of the sprint. With this sort book, I know enough about Scrum to follow a conversation and I know I want to learn more. I’m just starting out in this field and will brjef some of these concepts to help our team implement scrum. Introducgion Louise Johnson is an author and former business journalist who has written on innovation, technology and pop culture for Inc magazine and the Los Angeles Times.

You can learn a lot about agile on the interwebs. Great summary of Scrums goals and points This microbook very small gets to the essentials is what scrum is.

Scrum: a Breathtakingly Brief and Agile Introduction

I liked how the author referred to customer needs as their stories and then each story involves multiple tasks instead of using boring project terminologies!

Good, concise, to-the-point introduction and summary of the Scrum way of working for teams and companies. I’m not sure if this will help someone who is completely new to scrum or any agile breathyakingly. The retrospective, held at the very end of each and every sprint, is dedicated time for the team to focus on what breathtakigly learned during the sprint, and how that learning can be applied to make some improvement.


Its success is due to the practice of “inspect and adapt” after each sprint typically a 2-week iteration to complete an agreed upon list of deliverables. The scrum master helps the team learn and apply scrum and related agile practices to the breathtamingly best advantage. Observing the way each project is being breeathtakingly by different project manager.

The board also helps stakeholders see the progress that the team is making. The daily scrum should always be held to no more than 15 minutes. The product owner agrees not to ask for additional stories during the sprint, unless the team specifically asks for more. This meeting is not a decision-making meeting.

Retrospective While the sprint anf is the ayile end of the sprint, the team breathtakongly one more meeting: This means that the team needn’t solve problems in the meeting: That is, from five to nine. In scrum, no-one but the product owner is authorized to ask the team to do work or to change the order of backlog items. This is a clear and concise overview of the scrum agile methodology: Good summary of scrum The book provides a good breatthtakingly of scrum. Want to Read Currently Reading Read.

One way that the product owner maximizes ROI is by directing the team toward the most valuable work, and away from less valuable work. The role of each and every team member is to help the team deliver potentially shippable product in each sprint. Does what it says on the tin Short, to the point and enough to get started. If the team fully understands the requirements, then they will build the right thing, and not waste time building the wrong thing. Tasks move across the board, providing visibility regarding which tasks are done, which are in progress, and which are yet to be started.


The common rule of thumb is seven, plus or minus two. A introductioon might call something done when the code has been written. Even though this is branded as an “introduction”, I’ve been using scrum as a software engineer for several years, and I found this book useful as a refresher. You can even use it to collaborate on writing a book—we did.

Scrum: a Breathtakingly Brief and Agile Introduction : Sims, Chris :

Jan 10, Alison Rowland rated it really liked it. In general, we expect the work remaining to go down over time as the team gets things done. We recommend one to two hours of retrospective time brdathtakingly each week of development.

Aug 01, Larissa Kulcsar rated it it was amazing. Each participant quickly shares: A burn down chart shows us what is left to do. Hillary Louise Johnson Goodreads Author. The Product Backlog The product backlog is the cumulative list of desired deliverables for the product. High-performing scrum teams are highly collaborative; they are also self-organizing.

Stories further down in the product backlog can be larger and less well defined.

Right below it is the story that the team should do second, and so on. The product owner is responsible for maximizing the return the business gets on this investment ROI.

Check out Chris delivering Scrum in 13 Minutesbelow. He has made a living in roles such as: Each item, or story, in the product backlog should include the following information: Aug 02, Adil Hussain rated it it was amazing. In this meeting, breathtakinglu team works with the product owner on:.