Please enable JavaScript.

Coggle requires JavaScript to display documents.

Chapter 6 Phases of Scrum Process - Coggle Diagram

- - - - Enhancements can rapidly be recognized and carried out throughout each iteration, making it possible for the next iteration being a minimum of marginally better than the previous.
        
        Planning and Requirements:
        
        Like most any improvement project, step one is enduring a preliminary preparation phase to map out the specification documents, create software or maybe hardware requirements, moreover typically get ready for the upcoming phases of the cycle.
        
        Design and analysis:
        
        Once preparation is done, an examination is conducted to nail down the correct internet business logic, database models, and the way will be needed at this time in the venture. The design phase in addition happens here, starting any technical requirements (languages, services, data layers, etc), which will probably be used in an effort to meet up with the requirements of the evaluation phase.
        
        Implementation
        
        With the preparation along with analysis into position, the real implementation and coding process could now start. All preparation, specification, along with design docs up to this point are coded and also implemented into this original iteration of the venture.
        
        Testing
        
        Once this power build iteration is coded and implemented, the next thing is going through many testing procedures to determine and find some potential issues or bugs which have cropped up.
        
        Evaluation
        
        Once all prior stages were finished, it's time for a comprehensive analysis of advancement up to this particular point. This enables the whole team, and also customers and any other external people, to check out where task is at, where it must be, what can or even should change, so on.
- - - - It is the assignment of the Scrum Master to dispose of these Blockers.
        
        he Blocker is passed on to the next Team Members in the Daily Scrum Meeting and recorded in the Impediment List
  - - - What did I do yesterday that helped the Development Team meet the Sprint Goal?
      - What will I do today to enable the Development to group meet the Sprint Goal?
      - Do I see any hindrance that anticipates the Development Team or me from meeting the Sprint Goal?
- - - - he vision needs to describe in what ways the product will change and influence the business environment and what are the benefits to the customer. It also needs to explain how the product will be introduced to the market. Sometimes planning needs to have phases too
        
        After planning, the highest prioritized work is getting the funds, creating an initial product backlog along with the release plan. After that, in this phase team needs to determine technicalities, architecture in business environments and expectations from the project.
  - - - After every sprint in the development phase, product owner reviews if the desired functionality is achieved and what is the right time to release the product.
        
        After all these inspections and reviews, the Product Owner establishes if the
        conditions for release are met and the project enters the Release phase.
        
        This phase is made of two different kinds of activities.
        
        The first one is the activity that sets additional requirements for the product backlog. These requirements should polish the product and convert it from potentially shippable to an actual releasable product. If the development phase failed to meet any of the requested assignments, the product owner addresses more sprints to fix this
        point.
        
        Another activity in the release phase refers to one or more sprints that need
        to be added as a consequence of inadequate increments created during the development sprints.
        
        The release phase can be established only after the development team creates working functionalities that suffice final product backlog requirements.