Please enable JavaScript.

Coggle requires JavaScript to display documents.

PMI-ACP Agile Planning - Coggle Diagram

- - - - feature that must be released
        are constrained by a release date
      - selected features dipend on available iterations
    - - no date constraint, just features to
        be included inside the release
- - - - benefits of the
        business case
        
        everyone uderstands what
        customer is trying ti achieve
        
        simplify decision makign
        by setting clear objectives
        
        keep the project team focused
        on meeting the customer's overall
        objectives
        
        value-driven
        
        values to achieve must be clear to all members
        of the team. Tradional is plan-driven: team is focused
        on respect the planning
        
        criteria for judging the success
        of a project
      - developed by the customer
      - questions about a proposed
        project
        
        economic impact
        
        roi
        
        does the project can pay for itself?
        
        technical impact
        
        who has technical ability
        
        operational impact
        
        does the customer have the
        ability to mantain the product/serivce?
        
        if not project may be considered
        not feasible
        
        political impact
      - key components that need
        to feature in a business case
        
        opportunity
        
        chance to create value
        
        goals
        
        reasons why a project
        shuld be implemented
        
        ispire a team
        
        clarify the value that should
        be created
        
        strategy
        
        plan to achieve goals
        
        milestones
        
        siginificant point in devlopment
        
        make easier to track progress
        
        investment
        
        costs based on each milestone
        
        expected payback
        
        roi
        
        how long it will take the payback
        to be realized
    - - extent the business case
        and product vision
      - focus only on functionalities that
        is of direct value to the customer
      - use cases
        
        overview of a project scope
        
        user interaction with the system
        
        required results
        
        response to system errors (exception)
      - define minimal marketable features
        
        minimial product that can be released
        
        a list of minimal features required
    - - break down the project's high-level
        into specific, descrete requirements
        for particular product function
      - large user stories
        
        called epics
        
        divide into smaller user stories
    - - how product can capitalize on
        the opportunities and fullfill the goals
        of the business case
        
        list all involved stakeholders
        
        determine how to approach
        development process
        
        what will be delivered
      - high level requirements
        definition
        
        common understanding of
        what's required
        
        without limiting
        te team creativity
        
        cannot accept "I'll know it when I see it"
        from the customer
        
        some requirements are needed
        in order to start development
        
        product vision requirements are expected
        to remain the same during the project
      - how to determining a product vision
        
        interview to the customer who
        had initial idea
        
        interview in small team
        
        ask open-ended question
        
        let people responde
        in their own words
        
        facilitate different point of views
        
        minimum and maximun requirements
        
        evalutate risks and benefits
        
        general meetings with
        all stakeholders
        
        gather perspectives
        
        what the product shgould do
        
        core lement in the envisioning phase
        
        record hilgh-level requirements
        
        express the vision statement
        beloging to the requirements
        
        es. by asking to the project team
        to create a marketing blurb for the
        product
        
        very succinct and clear
        
        should focus on how product will add value
      - acceptance criteria
        
        customer will use to judge
        the success
        
        condition about
        
        quality and value
        
        non negotianable
        
        scope
        
        schedule
        
        budget