Escolar Documentos
Profissional Documentos
Cultura Documentos
Agile approach:
- Work as a team
- Work in short iteration
- Delivering each iteration
- Focus on bussiness priority
- Inspect and adapt
Scrum benefit:
- Delighted customer
- Imporve return to investment
- Reduce cost
- Fast result
Scrum frameworks
- Roles
o Product owner
o Scrum master
o Development team
- Activities
o Sprint
o Sprint planning
o Daily scrum
o Sprint exec
o Sprint review
o Sprint retrospective
o Product backlog grooming
- Artifacts
o Product backlog
o Sprint backlog
o Potentially shipable product increment
- Rules
1. Product owner has a vision of what he wants to create (cube). Cube can grow and the
activity called grooming
2. Cube broke down into set features collection and called product backlog
3. The number of items in the product backlog is likely to be complete in a short duration sprint
4. Development team determining a subset of the product backlog items and complete sprint
planning
5. Team members create a second backlog during sprint planning called sprint backlog
6. Sprint backlog describes through detailed tasks, how the team plans to design, build,
integrate, and test the selected subset of features
7. Sprint exec-> the dev team performs the task to realize the selected features to generate
potentially shippable product increment
8. Team members conducting a synchronization, inspection, and adaptive planning activity
known as daily scrum
9. Sprint review -> the stakeholders and scrum team inspect the product
10. Sprint retrospective -> scrum team inspects the scrum process being used to create the
product
Product Backlog
Product backlog (the heart of scrum)= an ordered list of everything that is known to be needed in
the product
- Detailed appropriately
- Emergent
o As long as the product being develop/maintained, the product backlog is never
complete/frozen
o Constantly emerging over time
- Estimated
o Each item has a size estimate
o Very large items near the bottom may be estimated in T-shirt sizes
- Prioritized
Definition of ready:
Sprint
Sprint= work is perfoermed in iterations or cycles of up to a calendar month
- Sprint are timeboxed so they always have a fixed start and end date
- Sprint timeboxed benefit:
o Established a WIP limit
o Forces prioritization
o Demonstrate progress
o Avoid unnecessary perfectionism
o Improves predictability
o Ease of planning
o Fast feedback
o Bounded error
o Frequent checkpoints
Definition of done:
- Design reviewed
- Code completed
o Code reafactored
o Code in standard format
o Code is commented
o Code checked in
o Code inspected
- End user documentation updated
- Tested
o Unit tested
o Integration tested
o Regression tested
o Platform tested
o Language tested
- Zero known defects
- Acceptance tested
- Live on production servers
User Story
User stories card= a common template format for writting users to specify the user role, the goal,
and the benefit
- Independent
- Negotiable
- Valuable
- Estimable
- Size approriately
- Testable
- Non functional requirement
Scrum Roles
Scrum Roles(consist one/more Scrum teams):
o Oversee grooming
o Participate at sprint planning, sprint review, and sprint retrospective
o Answer questions
o Attend daily scrum if possible
o Review features
o Stakeholder meetings
- Scrum master = helps everyone involved understand and embrace scrum values, principles,
and practices
o As a coach, providing process leadership and helping the team to develop their high
performance
o Helps the team resolve issues and make improvements
o Servant leader
o Process authority
o Interference shield
o Change agent
- Development team
o During sprint execution-> dev team members perform the hands on creative work of
designing, building, intergrating, and testing product backlog items into increment of
potentially shippable functionality
- Estimate as a team
- Estimates are not commitment -> the estimates ough to be realistic measure
- Focus on accuracy not precision
- Use relative versus absolute sizes
Technical Debt
Consequences of tech debt: