Agile

Annotations:

• Is to possess the ability to both, create and respond to chage in order to profit in a turbulent environment.

1. Cutting Edge
2. Shrinking the "time to market"
3. Reduction of cost (similations and automation)
4. Customer value is a delivered
5. Adaptive

1. Customer Satisfaction

   Annotations:

   • Satisfy the customer through early and continues delivery of throuble software.
2. Welcome changing requirements

   Annotations:

   • Essential to approach product development in an adaptive manner that enables change incorporation and fast product lifecycles.
3. Deliver working software frecuency

   Annotations:

   • Delivering working in increments
4. Work together daily

   Annotations:

   • Collaborate enviroment
5. Build projects around motivated individuals

   Annotations:

   • Give them the enviroment and support they need, and trust them to get the job done.
6. Face to face

   Annotations:

   • The most effective method team, is face to face.
7. Working is the mesuare of progress

   Annotations:

   • The mayor value is develop process
8. Sustainable development

   Annotations:

   • The sponsors, developers, and users shoukd be able to maintain a constant pace indefinitely
9. Technical excellence and good design enhances Agility

   Annotations:

   • Some of the ways of ensuring this area continuous integration, refactoring, and incremental re-architecture.
10. Simplicity

    Annotations:

    • The art of monitorizing the amount of work not done-is essencial, Small feature sets, focusing on client due, ensuring good upfront desing/model, etc.
11. Self-organizing teams

    Annotations:

    • Trust in team for develop key projects solutions.
12. Regular intervals

    Annotations:

    • Reflects on how to become more effective and then tunes and adjusts its behavior accordingly.

1. Waterfall model

   Annotations:

   • For ordered and predictable projects in which all the requiremets are cleary defined and can be estimated accurately.
   1. Inspect-adapt cycles as opposed the command-and-control structures.
2. Emphasis
   1. People
3. Suited for
   1. Unpredictable domains
   2. Iterative style

      Annotations:

      • Shippable deliverable

1. Agile Manifesto
   1. Lean Kanban
      1. Singboard assist and track producction
   2. Xtreme Programming
      1. Makes possible to keep the cost of changing
         1. Increment development
         2. Flexibility scheduling
         3. Automated test codes
         4. Close collaboration
         5. All involved
   3. Crystal methods
      1. People centric, lightweight and easy to adapt
   4. FDD
      1. Fast process
   5. Test Diven Devolopment
      1. Fist codes the test
   6. TDD
      1. ATDD
         1. Acceptance test
      2. DTDD
         1. Developer test
   7. Adaptive software development

      Annotations:

      • constant adaption of processes to work at hand.
      1. Grew out of rapid application
   8. Agile Unified Process
      1. Work in the best quality
   9. Domain value

Annotations:

• Must be addressed and managed throughout a Scrum project

1. Organization
   1. Roles
      1. Core Roles

         Annotations:

         • -Are involved in producing the project's product or service. -Individuals assigned are fully committed to the project. -Responsible for the success of each project iteration and of project as a whole.
         1. Product Owner
            1. Maximun business value
            2. Customer requirements
            3. Business justification
            4. Voice of customer
         2. Scrum Master
            1. Appropriate environment
            2. Guides, facilites and teaches
            3. Clear impediments
            4. Scrum processes are being followed
         3. Scrum Team
            1. Understant Product Owner specified requirements
            2. Deliverables
      2. Non-Core Roles

         Annotations:

         • Optional and may include all team members who are interested in the project. No formal role in the project main, but may interface with the team. Not be responsible for the success of the project.
         • Optional, no formal role, but may interface with the team. Not be responsible for the success of the project.
         1. Stakaholders(s)
            1. Customer, Users and Sponsors
            2. Interface Scrum Core Team
            3. Collaborative benefits
         2. Vendors
            1. Individual organization
            2. Provide products and services competencies
         3. Scrum Guidance Body
            1. Documents & grop of experts
            2. Defining objectives
            3. Guides Product Owner, Scrum Master & Scrum Team
2. Business justification

   Annotations:

   • Business assessment. Key decision makers to business need
   • Product Owner is the maximum responsable
   1. Value-driven delivery
      1. Uncertainty of results or outcomes
         1. Impossible to guarantee Project's sucess and completion
            1. Scrum attempts to start delivering results as early in the project as possible
               1. This provides an opportunity for reinvestment
3. Change

   Annotations:

   • Maximize benefits change minimize negative impacts
   1. Requirements Churn
      1. Welcome changes
         1. Scrum Team members view deliverables to change requirements
4. Risk

   Annotations:

   • Uncertain event
   1. Positive impact

      Annotations:

      • Opportunities
   2. Negative impact

      Annotations:

      • Threats
   3. lifecycle
      1. Identified
      2. Evaluated
      3. Proper course of action is determined upon and acted upon
   4. Assessed & Respond
      1. Probability
      2. Possible impact
      3. High probability & impact value detmined multiplying factors
         1. Once identified - important to understand
5. Quality

   Annotations:

   • The ability to completed deliverables and acceptance criteria
   1. Prioritized Product Backlog
      1. Incremental fashion Sprints
         1. Errors
            1. Quality part of Sprint
               1. Issues are listed in the Product Backlog
                  1. Constant discussions between Scrum Core Team and Skateholders, customers and users

Annotations:

• Product Backlog of priorized requirement. Product owner for priorized requirements.
• 19 process grouped into 5 phases.

1. 5 Phases
   1. Inputs
   2. Tools
   3. Outputs
   4. On particular project, organization or Indistry
   5. Scrum Process
      1. Initiate
         1. Create Project Vision

            Annotations:

            • First process Project Business is reviewed to create Project Vision Statement Product Owner
         2. Identified Scrum Master and Skateholders

            Annotations:

            • Scrum Master is identified
         3. Form Scrum Team

            Annotations:

            • Scrum Team members are identified Product Owner responsible for selecting team members, often does so in collaboration with the Scrum Master
         4. Develop Epic (s)

            Annotations:

            • Project Vision Statement serves as the basis for deveping Epic User Group Meetings may held to develop Epic(s)
         5. Create Prioritized Product Backlog

            Annotations:

            • Epic(s) and Unrefined User Stories refined and elaborated and prioritized to create a Prioritized Product Backlog
         6. Conduct Release Planning

            Annotations:

            • Scrum Core Team reviews the User Stories in the Prioritized Product Backlog to develop a Release Planning Schedule
      2. Project Plan and Estimate
         1. Create User Stories

            Annotations:

            • User Stories and their related User Story Acceptance Criteria are created Usually written by Product Owner Designed to ensure that the customer's requirements are clearly depicted and understood Involves Scrum Team members creating the User Stories Incorporated into the Prioritized Product Backlog
            1. Inputs
               1. Scrum Core Team
               2. User Stories
            2. Tools
               1. Numerous estimation methods
               2. Wideband Delphi

                  Annotations:

                  • Is a group-based estimation technique Who long is the work Individual within a team anonymously provide estimations for each item Initial estimates are plotted on a chart Teamdiscusses the factors that influenced their estimates Rounds for final estimate
               3. Planning Poker

                  Annotations:

                  • Uses concensus Estimate relative sizes of User Stories Effort requiered to create them
               4. Fist of Five

                  Annotations:

                  • Group concensus building technique After initial discussion on a given item for estimation Scrum Team members are each asked to vote. Value in using this technique is not only consensus building. Driving discussion because team members are asked to explain the reason for their estimates. Team members vote bases on their level of agreement and desire for discussion.
                  • Discussion Product Owner will indicate some sizing categories on the wall (Small, Medium, Large) or numbered. Transparent, visible to everyone, easy to conduct.
               5. Affinity Estimation

                  Annotations:

                  • Used to quickly estimate large nu Team places User Stories on a wall or other surface, in order from small to large Each team members begins with a subset of User Stories from the overall Prioritized Product Backlog to place by relative size
            3. Outpts
               1. Estimate User Stories
            4. Estimate User Stories
            5. Commit User Stories
            6. Identify Task processes
         2. Approve, Estimate, and Commit User Stories
         3. Create Tasks
      3. Impliment
      4. Review and Restropect
      5. Realese