Everand Logo

Welcome to Everand!

  • Discover millions of ebooks, audiobooks, and so much more with a free trial

    Only $11.99/month after trial. Cancel anytime.

    The Scrum Guide Unfolds: Agile Software Development, #2
    The Scrum Guide Unfolds: Agile Software Development, #2
    The Scrum Guide Unfolds: Agile Software Development, #2
    Ebook104 pages1 hour

    The Scrum Guide Unfolds: Agile Software Development, #2

    By Maik Seyfert

    4/5

    ()

    Read preview

    About this ebook

    Scrum is based on a set core of values, principles, roles, and practices. This book sets to highlight these different aspects of Scrum. It is a good read to people new to Scrum and want to learn what it is all about. Experienced people who have used Scrum before will also find the information helpful as it dives deeper into the practices in Scrum.
    This book is not meant to replace the Scrum Guide. It is a complementary resource meant to help teams implement Scrum practices. It is meant to help Scrum teams understand the basic principles behind Scrum and implement them for maximum effectiveness. What is covered in this book goes beyond the Scrum Guide to offer deeper insights into the benefits and pitfalls of the concepts, tools, and practices. 
    Table of contents

    Introduction
    1. What is Scrum?
    1.1 History of Scrum
    1.2 Underlying Principles of Scrum
    1.3 Strengths and Benefits of Scrum
    1.4 What Projects are Best Suited for Scrum?
    1.5. Scrum Pillars
    1.6. Scrum Values
    -
    2. The Scrum Roles and their Interactions
    2.1. Product Owner
    2.2. The Scrum Master
    2.3. Characteristics of a great Scrum Master
    2.4. The Developer Team
    2.5. Factors limiting the effectiveness of a team
    2.6. Characteristics of a great development team
    -
    3. Ceremonies and Timeboxes
    3.1. Scrum Release Planning Meeting
    3.2. The Sprint
    3.3. Sprint Planning
    3.4. Daily Scrum
    3.5. Sprint Review
    3.6. Sprint Retrospective
    3.7. Backlog Refinement/Grooming
    3.8 The Three Amigos
    -
    4. Scrum Artifacts
    4.1. The Product Backlog
    4.2. Sprint Backlog
    4.3. Software Increment
    -
    5. Transparency
    5.1 Artifact Transparency
    5.2. Transparency supporting factors
    5.3. Definition of Done
    5.4. How to Profit from Scrum’s Transparency
    -
    6. Scrum Implements the Agile Manifesto
    6.1. Individuals and Interactions over Processes and Tools
    6.2. Working software over comprehensive documentation
    6.3. Customer Collaboration over Contract Negotiation
    6.4. Responding to Change over Following a Plan
    Conclusion

    About the Author

    The author, Maik Seyfert, is an Agile practitioner and coach with 10 years real project experience, which he offers to everyone with this book.

    LanguageEnglish
    PublisherMaik Seyfert
    Release dateJan 13, 2017
    ISBN9781386299547
    The Scrum Guide Unfolds: Agile Software Development, #2

    Related to The Scrum Guide Unfolds

    Titles in the series (3)

    View More
    View More

    Related ebooks

    Software Development & Engineering For You

    View More
    View More

    Related podcast episodes

    Related articles

    • Article

      AGILE: It Is All About Trust

      Oct 22, 2019

      AGILE: It Is All About Trust
      6 min read

    • Article

      Driven By Skills

      Mar 19, 2020

      Driven By Skills
      4 min read

    • Article

      Change Sustainability Your ROI Health Check

      Mar 28, 2019

      Change sustainability programs are as unique as each of the workplace projects themselves. They can be developed either to dovetail into the end of a change program where businessas-usual kicks in, or they can be integrated into a prototype rotation

      5 min read

    • Article

      Principles of Technical Leadership

      Mar 1, 2022

      IT staff is more than just a number on a spreadsheet. This information is valuable, but it does not tell the whole story. We’ll also need to know about your team’s project history, current (non-hired) CV, and the skills and positions they have—and wa

      2 min read

    • Article

      The Road Best Travelled

      Feb 25, 2018

      The Road Best Travelled
      3 min read

    • Article

      Growing Communities of Practice

      Sep 1, 2019

      According to the SAP Digital Transformation Executive Study, 80 per cent of companies that have embraced digital transformation have experienced increased profitability. So why have only 21 per cent of companies completed their digital transformation

      5 min read

    • Article

      Better Rewards, Fewer Risks

      Mar 19, 2018

      Better Rewards, Fewer Risks
      4 min read

    • Article

      When Teams Create Themselves

      Apr 12, 2022

      When Teams Create Themselves
      4 min read

    • Article

      Key Considerations For Organisations Looking To Transform Customer Experience

      Jul 7, 2019

      Businesses can’t simply decide to transform one day, then jump straight changing for change’s sake. It’s essential to plan the transformation carefully and understand the barriers and opportunities that could arise. Equally, some research suggests bu

      2 min read

    • Article

      Sustainability Tools: The Regenerative Compass

      Jan 1, 2024

      We are well into what climate experts are calling ‘the decisive decade’ for sustainability and Net Zero commitments. And yet, significant action and momentum are missing in most organizations. Even in companies that have made bold commitments for 203

      4 min read

    • Article

      Defining success

      Jun 24, 2019

      With most architectural projects spanning at least 12 months, end outcomes can be an irrelevant concept in defining success on a day-to-day basis. And what about when a project falls through or the developer pumps the brakes and changes scope? The ar

      3 min read

    • Article

      Get Your Priorities Straight: The Hierarchy of Purpose

      May 1, 2017

      Prioritizing is usually seen as an individual skill that some are good at, others not so much. We prioritize whenever we think about how we will spend our time today, this week, this month — or this year. But the fact is, prioritizing is also a key o

      6 min read

    Related categories

    Reviews for The Scrum Guide Unfolds

    4/5

    1 rating0 reviews

    What did you think?

    Tap to rate

    Review must be at least 10 words

      Book preview

      The Scrum Guide Unfolds - Maik Seyfert

      What is Scrum?

      Scrum is a simple and flexible software development methodology or framework. Scrum framework introduces alternatives to traditional project management systems such as Waterfall or Sequential development. Unlike the other methodologies, Scrum is an agile framework which is highly optimized to react to any changes within the development process to suit the vision of the product owners.

      Among all agile methodologies, Scrum is the most popular. It is adaptive, iterative, flexible, fast and effective in delivering value to the development process. Versatility of Scrum ensures that it is not only used in software development but across other industries including those offering services. It can be used in all types of industries and in various projects from simple ones to more complex ones. Scrum ensures that a project archives continuous progress through transparent communication and collective accountability.

      In Scrum, there are numerous opportunities for the product owners and the team to access the direction the project is taking within the development cycle. This is one of the major benefits of this methodology. Contrast this to the other methodologies where the product owner who has the vision for the product isn’t in constant communication with the team thus leading to the possibility of a mismatch between the vision and the product. This can be quite expensive in terms of time and money. In Scrum, the team is in constant communication, any impediment, weakness, and risks are easily spotted and remedial actions taken.

      History of Scrum

        The concept of scrum dates backs to the mid 80’s when Hirotaka Takeuchi and Ikujiro Nonaka, two acknowledged management thinkers presented a paper titled ‘The New Product Development Game.’ these two used the word Scrum to denote the importance of a team. Scrum is used in rugby, which is a team sport. In rugby scrum, teammates come together in an interlocking manner to restart play. They thus drew parallels between a team sport like rugby and working as a team in new product development. The team passes the ball back and forth till they achieve their common goal. The paper went further to show that when teams are fed with objective rather than task, they self-organize in a manner that enables them best archive these objectives. They argued that the best performing teams are those that are given the direction to take and are left to devise their own strategies for achieving the joint objective. It can be said that teams require a high sense of autonomy to achieve excellence.

        In the mid 90’s, Ken Schwaber and Jeff Sutherland picked on the scrum concept and elaborated it especially on its applicability to software development. They did a presentation titled ‘The SCRUM Development Process’ at the Object-Oriented Programming, Systems, Languages & Applications (OOPSLA) conference held in 1995 in Austin, Texas. At this point, the Scrum methodology gained a strong foothold. Many experts came in and refined it. It was adopted by many organizations globally.

        In February 2001, 17 software development leaders among then Ken and Jeff created the Agile Manifesto for Software Development. Shortly after, the Scrum Alliance was founded.

        There have been important contributions to Scrum by Mike Cohn who introduced user stories as a tool for describing client goals of work. Story points were also introduced as a way of measuring the quantity of work. In case I have lost you with these terms, we shall be looking at them in the next chapter.

      Underlying Principles of Scrum

      The scrum principles must be adhered to ensure that the Scrum framework/methodology is implemented effectively. This then ensures that the objectives of the project are achieved. Scrum principles can be applied in various projects not necessarily software development with much success. The six Scrum principles are:

      Empirical Process Control

      Empirical control means that decisions in Scrum are made by observing and experimentation rather than detailed upfront planning. To do this, we need transparency, inspection and adaptation. In transparency, information flows freely throughout the organization thus creating an open culture. Inspection is archived through the use of a common Scrum board as well as a collection of feedback from all stakeholders. The product owner will also inspect deliverables. After transparency and inspection, all stakeholders will learn and hence adapt by making the necessary improvements.

      Self-organization

      In Scrum, teams that are self-organized deliver greater value than others. This is because of the feeling of shared ownership. When a team buys into the vision of the product owner, and are allowed to self-organize in the best way to achieve the desired goals, they are likely to perform much better. They also accept greater responsibility

      Enjoying the preview?
      Page 1 of 1