Please enable JavaScript.

Coggle requires JavaScript to display documents.

Chapter 2 Scrum Basics - Coggle Diagram

- - - - This last point is important as the concept of “working software” implies that at the end of each sprint, the project team must be able to deliver value to the customer.
        
        Typically, each sprint lasts for four weeks.
        
        Although, this is only a rule of thumb. The length of an individual sprint depends on a number of factors. But, in general, four weeks is a good number. It should be noted that one-week sprints may not provide you with enough time to complete tasks while sprints longer than four weeks may drag the project on needlessly.
    - - The Sprint Planning Meeting consists of determining the objectives for the sprint that is about to start.
        
        Given the collaborative nature of Scrum, the objectives, or user stories to be covered will be decided by the team itself.
        
        Once the work to be done has been decided at the Sprint Planning Meeting, the team will begin working.
    - - This meeting consists of having a short meeting, about 15 minutes in length, in which the issues affecting the Development Team are brought up. This could be anything related to the work being done such as issues dealing with equipment, perhaps a lack of clarity on the tasks being done, or a team member asking for help.
        
        This meeting is very much informal in nature. However, this does not mean that it is not serious.
    - - At the Sprint Review Meeting, the Development Team presents the outputs of that sprint to the customer.
        
        The customer is then able to see where the project is headed and how the team has been able to meet the acceptance criteria established as the measure of success for the project.
    - - The Sprint Retrospect Meeting consists of a debrief that the Development Team engages in, in order to discuss what went right, what needs to be improved, and what issues they encountered throughout the sprint.
        
        The Sprint Retrospect Meeting can also segue into the Sprint Planning Meeting.
        
        It’s important to note that change requests from customers should be addressed at the beginning of a new sprint so as to avoid altering the planning for the sprint currently in progress.
      - The process of Sprint Planning Meeting, sprint, Sprint Review Meeting, and Sprint Retrospect Meeting is called “iteration”. This cycle is repeated as many times as needed in order to complete user stories.
        
        Once all user stories are completed and the product is fully functional, then the project can be considered to be over.
- - - - Since a project may have multiple user stories, the project cannot be deemed as completed until all user stories have been covered.
- - - - this is the “voice of the customer,” meaning that the Product Owner will be in constant communication with the customer and to relay this information to the Scrum Master and Development Team
        
        Generally, the Product Owner will communicate with the Scrum Master and then the Scrum Master will incorporate any additional information to the Development Team
        
        The Product Owner is generally the first player on the team and will most likely be in charge of selecting the Scrum Master and the Development Team.
    - - The Scrum Master is known as a “subservient leader”
        
        The Scrum Master is intended to act as coordinator in order to ensure that all activities are running smoothly and that the Development Team has all the tools they need in order to do their job.
        
        In addition, the Scrum Master must develop a good sense for dealing with issues proactively before they become any type of serious hindrance to the project’s
        development.
    - - these are the individuals who are actually in
        charge of creating the product that the project aims to develop
        
        They are skilled in their craft and are more than likely specialists in their field. They may have some limited knowledge and experience in Scrum, whereas, the Scrum Master and the Product Owner must be very well-versed in Scrum methodology.
        
        The Development Team is in charge of deciding what work will be done and when it will be done. This is what happens at the Sprint Planning Meeting. The ultimate decision of what to include and what not to include is the result of the discussion among the Scrum Master and the Development Team.
        
        Finally, the Development Team generally consists of 4 to 8 members. Any team larger than 10 members should be broken up into two smaller groups, or perhaps subgroups, in order to facilitate communication and coordination among them.
- - - - Sprints typically last between 1 and 4 weeks and can even take as little as one day. They’re considered to have a short development cycle, so shouldn’t take longer than 4 weeks.
        
        The planned economic value is determined by how long the Sprint is, so if it takes longer than originally thought, then that means more money spent.
  - - - The Product Owner presents the Product Backlog, explains the tasks, and asks the team to choose the tasks they want to work on. The Scrum Team also figures out the requirements that will be used to support said goal and will be used within the Sprint. Plus, the Scrum Team will identify the individual tasks it will take for each specific requirement.
  - - - During this meeting, the Scrum Team members coordinate on their priorities. They talk about what is most important to get done during the day, what they completed the day before, and if there are any roadblocks they might run into when doing the current day’s work.
  - - - The Product Owner then determines whether the whole Sprint Backlog is covered or not. It’s possible that something might be put back into the backlog if not done correctly.
  - - - They discuss what went well, what possible changes they could make, and how to make those changes. They also discuss how to make the team work more efficient if there were any issues going on. It’s important to speak up about issues, otherwise it could cause problems later on down the road that would prevent the project from continuing.
- - - - Transparency is vital as it is important that those who are responsible for the outcome of a given process have a clear understanding of how it is proceeding at every step along the way
        
        Additionally, transparency is also important to ensure that anyone else who needs to see what is going on can follow along as well. The end goal is that any observers will all have the same general understanding of whatever it is they are seeing.
    - - Scrum users are frequently required to use Scrum artifacts as they progress towards a goal in order to determine potential variances that may be undesirable to that goal.
        
        These inspections should not be so frequent that the get in the way of the work that is being completed and are instead most effective when they are performed diligently by those who are skilled at inspecting this point of work.
    - - When an inspector finds that some aspect or aspects of the process are deviating more than is acceptable, or that the resulting product will ultimately be unacceptable then the process must be changed as quickly as can be managed to avoid additional deviation as much as possible.
        
        When adaptation is required, there are several specific events that take place as part of the Scrum process, and they include the Sprint Retrospective, Daily Scrum, Sprint Review and Sprint Planning.