Você está na página 1de 7

--------------------------------------------------------------------------------------------------------------------------------------

Agile approach:

- Work as a team
- Work in short iteration
- Delivering each iteration
- Focus on bussiness priority
- Inspect and adapt

Scrum= is an agile approach for developing innovative products and services

- Scrum is based a small set of core values, principles and practices


- Why scrum?
o Can be use on complex software project with a lot of unknown than known
o Can be use to avoid big up front architecture design
o More balanced to design
o Make teams more cross functional

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

Good characteristic product backlog:

- 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

Collaborative grooming by:

- Internal stakeholders (bussiness owners, managers, program management)


- External stakeholders (customers, users, partners, regulators)
- Product owner
- Scrum master
- Development team
When grooming happens:

- Up front then ongoing as necessary


- Workshop during sprint
- After daily scrum
- During sprint review

Definition of ready:

- Bussiness value is clearly articulated


- Details are understood by dev team so it can make a decision to complete the PBI
- Team is staffed appropriately to complete PBI
- The PBI is estimated and small enough to comfortably be completed in one sprint
- Acceptance criteria are clear and testable
- Performance criteria are defined and testable

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

Short duration benefit

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

User story guidance:

- Independent
- Negotiable
- Valuable
- Estimable
- Size approriately
- Testable
- Non functional requirement

Scrum Roles
Scrum Roles(consist one/more Scrum teams):

- Product owner = the empowered central point of product leadership


o Collaborate with the dev team and stakeholders
o Maintains and communicates to all participants
o Responsible for overall success
o Manage economics
o Participate in planning
o Groom the product backlog

Product owner characteristic:


o Domain skills
 Is a visionary
 Knows not everything can be anticipated
 Has business and domain expertise (keahlian)
o People skills
 Has a good realtionship with stakeholders
 A negotiator
 A good comunicator
 Powerful motivator
o Decision making
 Empowered to make decisions
 Willing to make hard decisions
 Decisive
 Takes and economic view to balance business issues
o Accountability
 Accepts responsibility for the product
 Committed and available
 Acts like a scrum team member

Product owner daily life:

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

Scrum master characteristics:


o Knowledgeable
o Questioning
o Patient
o Collaborative
o Protective
o Transparent

Scrum master daily life:


o Each day organizing and facilitationg the scrum activities, including sprint planning,
sprint exec, sprint reviews, sprint retrospectives, and daily scrum
o Setting up the activities
o Overseeing their execution
o Enabling the rest of scrum team to perform to high value result

- 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

Dev team characteristics:


o Self organizing
o Cross functionally diverse and sufficient
o T shaped skills -> ability to work outside of core area, functional area,
discipline/speciality
o Musketeer attitude
o High bandwith communications
o Transparent
o Focused and committed

Dev team diversity:


o Cross functionally diverse
 Cross functional team members
 Different backgrounds
o Diverse perspectives
 Interpretations
 Strategies
 Mental models
 Preferences
o Better outcomes
 Faster solutions
 Better solutions
 Greater innovation

Estimation & Velocity


PBI estimation concepts:

- 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

Velocity= the amount of work completed each sprint

Technical Debt
Consequences of tech debt:

- Unpredictable tipping point


- Increased time to delivery
- Significant number of defects
- Rising dev and support cost
- Underperformance
Cause of tech debt:

- Pressure to meet a deadline


- Attempting tofalsely accelerate velocity
- Less testing
- Debt build on debt -> future tech debt builds quickly on tops of existing tech debt

Managing the accrual of tech debt

- Use good tech practices


- Use a strong definition of done
- Properly understand tech debt economics
- Debt builds on debt

Você também pode gostar