Amazon cover image
Image from Amazon.com

Scrum for teams : a guide by practical example / Dion Nicolaas.

By: Material type: TextTextSeries: Publication details: New York, New York (222 East 46th Street, New York, NY 10017) : Business Expert Press, (c)2018.Edition: First editionDescription: 1 online resource (xvi, 127 pages) : illustrationsContent type:
  • text
Media type:
  • computer
Carrier type:
  • online resource
ISBN:
  • 9781948198448
Subject(s): LOC classification:
  • QA76 .S378 2018
Online resources: Available additional physical forms:
Contents:
2. What is scrum? -- 3. Make the most of stand-ups -- 4. Everything on the board -- 5. Planning is half the work -- 6. Practices make perfect -- 7. Demo, demo -- 8. Look back! -- 9. Done, done, done, done, done -- 10. Power to the team -- Bibliography -- Index.
Abstract: Scrum is an agile framework for completing complex projects. This book gives examples, tools, and tricks to do Scrum well. For each trick it is explained why it helps. The practices themselves may be worth trying, but by understanding why it works the readers will be able to come up with their own ideas that work better in their organization and situation. All the practical examples in this book have helped someone, somewhere to become a part of a better Scrum team. Scrum's motto is: "Inspect and Adapt"; change small things one at a time and see what works. Scrum is not done by project leaders or managers, but really by the teams--to succeed in an organization, the teams must do Scrum well. If the teams do Scrum well, the whole organization will benefit from it. Scrum helps teams self-organize, which fits in well with developers, who usually don't like to be micromanaged. At the same time, Scrum can scale: Self-organized teams work together well, and one manager doesn't have to manage all the people. The lessons from this book help Scrum teams develop into autonomous, proud, and independent teams. Often teams fail to become powerful enough to change the organization, so they cannot perform to their full potential. A good team can lead the stakeholders into trusting them. They will then make plans based on the team's release planning instead of making roadmaps out of thin air, and thus make the organization much more predictable.
Tags from this library: No tags from this library for this title. Log in to add tags.
Star ratings
    Average rating: 0.0 (0 votes)
Holdings
Item type Current library Collection Call number URL Status Date due Barcode
Online Book (LOGIN USING YOUR MY CIU LOGIN AND PASSWORD) Online Book (LOGIN USING YOUR MY CIU LOGIN AND PASSWORD) G. Allen Fleece Library Non-fiction QA76.76.D47 (Browse shelf(Opens below)) Link to resource Available 9781948198448

1. Introduction -- 2. What is scrum? -- 3. Make the most of stand-ups -- 4. Everything on the board -- 5. Planning is half the work -- 6. Practices make perfect -- 7. Demo, demo -- 8. Look back! -- 9. Done, done, done, done, done -- 10. Power to the team -- Bibliography -- Index.

Scrum is an agile framework for completing complex projects. This book gives examples, tools, and tricks to do Scrum well. For each trick it is explained why it helps. The practices themselves may be worth trying, but by understanding why it works the readers will be able to come up with their own ideas that work better in their organization and situation. All the practical examples in this book have helped someone, somewhere to become a part of a better Scrum team. Scrum's motto is: "Inspect and Adapt"; change small things one at a time and see what works. Scrum is not done by project leaders or managers, but really by the teams--to succeed in an organization, the teams must do Scrum well. If the teams do Scrum well, the whole organization will benefit from it. Scrum helps teams self-organize, which fits in well with developers, who usually don't like to be micromanaged. At the same time, Scrum can scale: Self-organized teams work together well, and one manager doesn't have to manage all the people. The lessons from this book help Scrum teams develop into autonomous, proud, and independent teams. Often teams fail to become powerful enough to change the organization, so they cannot perform to their full potential. A good team can lead the stakeholders into trusting them. They will then make plans based on the team's release planning instead of making roadmaps out of thin air, and thus make the organization much more predictable.

COPYRIGHT NOT covered - Click this link to request copyright permission:

https://lib.ciu.edu/copyright-request-form

Mode of access: World Wide Web.

System requirements: Adobe Acrobat reader.

Title from PDF title page (viewed on September 5, 2018).

There are no comments on this title.

to post a comment.