Please enable JavaScript.

Coggle requires JavaScript to display documents.

PMI Agile Certified Practitioner Chapter 5. (Release and Iteration…

- - - - Comunication
        
        This refers to the customers confirmation that the history has been implemented correctly
      - Card
        
        Its just a token that represents the requirement for planning purposes
      - Conversation
        
        The details for each story are communicated via conversation
    - - Independent
        
        Ideally we want to be able to reprioritize an develop in any order thats why its better if they are independent
      - Negotiable
        
        The team should be able to discuss user stories with the product owner and make trade-offs based on cost and functionality
      - Valuable
        
        If we cannot determine the value of a feature the we should question why is even part of the project
      - Estimatable
        
        We have to be able to estimate the effort a feature is going to take
      - Small
        
        If the user story is small, its gonna be easier to estimate the amount of effort its development is going to take. also is going to be way easier to fix if it goes wrong. small means around 4 to 40 hours
      - Testable
        
        Having testable user stories is important for tracking progress… among other things obviously
    - - This is
        
        A visible master list for all the functional and nonfunctional that the project requieres
      - Prioritization of the user story backlog
        
        Uses
        
        Guiding the teams priorities
        
        Planning tool for managing iterations and releases
        
        Helps the team manage change requests
        
        Helps the team manage the risk remediation effort with features development
        
        Helps the stakeholders coordinate the project
        
        Keeps every one working towards the agreed goal
        
        Refining the backlog
        
        Its the process of keeping the backlog updated and accurately prioritize. Helps agile projects stay flexible to customer's needs
        
        Involves
        
        Progressively adding more adding more details
        
        Adjusting the estimates and priorities of the backlog`s items
        
        Adding new work
        
        Removing items that are not longer important
        
        Types of Changes that the backlog may need
        
        Add new stories
        
        Existing stories may need to be removed
        
        Existing stories may need to be reprioritize
        
        Existing stories may need to be resized
    - - Its a more accurate way of estimating the amount of that needs to be done. It uses a relative unit called story point
        
        By relative sizing, it means that if you think that one feature will take you the twice as much effort you give to that feature 2 story points and the other one you give it one
      - Story points are typically based on the Fibonacci Series, which is a natural occurring progression to describe how things grow
      - Guidelines for using story points
        
        The team should own the definition of their story points
        
        Story points should be all inclusive
        
        We Shouldnt have to add any extra time for testing or refactoring, instead our story points should include all the known activities needed to complete the task.
        
        The point sizes should be relative
        
        When disaggregating estimate, the total dont need to match
        
        If we need to decompose the tasks needed to complete a user story, the sum of the smaller task`s story points dont need to match to the original one
        
        Complexity, work effort and risk should all be included in the estimates
    - - Allow us to change our minds whenever we have new information about a story
      - Works for both epic and smaller user storys
      - Doesnt take a lot of time
      - Provides useful information about our progress and our and the work remaining
      - Is tolerant to imprecision in the estimate
      - Can be used to plan releases
- - - - The team elicits requirements from the stakeholders and ranks them
    - - Is a fixed - duration period of time in which a defined set of activities is done.
        
        Estimate ranges
    - - How long a task will take if all the peripheral work and distractions are removed.
    - - Process of assessing and prioritizing the business value of work items and then planning accordingly
    - - Process of adding more detail as new information emerges
    - - Evolution and elaboration of agile project plans in contrast with an up-front, traditional approach to project planning
    - - The only way we can be successful on such projects is to plan to replan
  - - - Agile planning is less of an up-front effort, and is instead done throughout the project
      - Midcourse adjustments are the norm
      - Trial and demonstration uncover the true requirements, which then require replanning
  - - - Tailor processes to the project's characteristics
      - Update the plan based on the project's priorities
      - Ensure encompassing estimates that account for risk...
      - Manage expectations...
      - Use appropriate estimate ranges to reflect the level of ...
      - Engage the team and the customer in planning
      - Base projections on completion rates
      - Plan at multiple levels
      - Factor in diversions and outside work
- - - - need to
        
        Gather the team, look at the backlog
        
        And ask
        
        Which of the top-priority stories in the backlog for this release can we commit?
        
        The total points for these stories become our initial velocity estimate
  - - - Slicing Compound Stories
        
        A compound story includes other independent stories within it
      - Slicing Complex Stories
        
        is
        
        One really big or complicated story; it doesn't include sub-stories.
        
        but
        
        It can't be completed in one iteration
    - - Breaking down any stories that are too large to be completed within one iteration
- - - - We select
        
        User stories that the customer has indicated are high priority and that we believe can be delivered within the iteration
    - - to
        
        to better judge our true progress and estimate the remainder of the project
    - - each
        
        User story
        
        needs
        
        Clear acceptance criteria
        
        They are...
        
        Explicit statements of how the customer will define "done" for each story
    - - will create
        
        More detailed bottom-up estimates to schedule the work
    - - Provide
        
        An early warning system for issues
      - Keep
        
        Everyone focused on the agreed-upon scope and iteration goal
      - Are
        
        timeboxed to 15 minutes
- - - - is
        
        An optional iteration that we can use to set the stage for our development efforts
    - - We have it because
        
        We need another effort after the deliverable is accepted to prepare it for release
    - - It begins once
        
        the preparatory work has been completed
  - - - A key tool that agile teams use to head off problems and resolve them as early as possible
        
        Divided in
        
        Risk-Based Spike
        
        Consist in
        
        Investigate and reduce or eliminate an issue or threat to the project.
        
        Architectural Spike
        
        Consist in
        
        Checking whether the approach the team hopes to use will work for the project
  - - - If none of the approaches we try are successful
        
        It consist in
        
        the remaining funds and resources from the project can now be directed to other projects that are awaiting resources.
  - - - Determine which stories will be done in which iterations for the upcoming release
    - - A meeting in which all the stakeholders are represented