Webinar 2nd edition of the secrets of agile software development from the executive perspective

20
The Secrets of Agile Software Development from the Executive's Perspective

Transcript of Webinar 2nd edition of the secrets of agile software development from the executive perspective

The Secrets ofAgile Software Developmentfrom the Executive's Perspective

Your Panel

Julieta Barrionuevo• Lead Quality Assurance

Engineer • Software developer and

project manager• BS in Systems

Engineering from the National Technological University of Argentina

• Certified Scrum Master

Hubert Smits• Management Consultant

with over 25 years experience

• Broad and deep experience in Agile Software Development

• Global reach and experience

• Certified Scrum Trainer

Your Referee

Alex Robbio• VP of Business Development at Belatrix

Software Factory• Certified Scrum Master • Extensive experience in the software

industry including roles as Developer, Architect and Project Manager

Agenda

• Introductions• A few words about Scrum• Scrum and Contracts• Scrum and Requirements• Measuring Progress• Closing

INTRODUCTIONAgile & Scrum

The Agile Manifesto

individuals and interactions over processes and tools

working software over comprehensive documentation

customer collaboration over contract negotiation

responding to change over following a plan

that is, while there is value in the items on the right,we value the items on the left more.”

kent beck - mike beedle - arie van bennekum - alistair cockburn - ward cunningham - martin fowler

james grenning - jim highsmith - andrew hunt - ron jeffries - jon kern - brian marick - robert c. martin

steve mellor - ken schwaber - jeff sutherland - dave thomas

scrum

potentially shippableproduct increment

sprint planning meeting• review product backlog• select features for sprint• task out features for sprint• find owner for tasks• owner estimates tasks• commit to 2-4 weeks of work

sprint backlogtasked out features assigned to sprint estimated by teamowned by team-members

product backlog:prioritized features

desired by customer

daily

sprint

2-4 weekssprint review meeting• demo features to all• retrospect with team

AGILE CONTRACTSCustomer – Vendor Relationship

Agile ContractsHighlights Pros Cons

Fixed Cost • Fixed scope & price• Billing tied to milestones

• “Predictable” cost• Risk passed to

vendor (in theory)

• Not flexible• Can build what you

needed 12 months ago and not what you need now

• Lot of work upfront• Low visibility

T&M • Staffing, virtual team extension, etc.

• Billed by the hour, usually monthly

• Client in control• Simple to negotiate• Flexible and agile• High visibility

• Harder to manage performance

• Requires more involvement from client

Agile with SLA • T&M billing• Performance tracking,

with rewards and penalties per sprint

• All of T&M• Better performance

management

• Tweaking goals to keep them motivating but fair

• Client highly involved

Agile Contracts

• Focus on results: working software, early, continuous

• Focus on predictability: track velocity per team

• Encourage teamwork: velocity increase = team bonus

• Spot problems early: velocity decrease = company penalty

• Keep it simple!

Agile Contracts Summary

Cost control Visibility Flexibility Productivity

Fixed cost (theory)(reality)

T&M

Agile with SLA

REQUIREMENTSCustomer Role in the Agile Project

User Stories

METRICSProject Performance

Individual Burndown Chart

Remaining work (days) Sprint 3

0

5

10

15

20

25

30

35

Date

Wo

rkin

g d

ays

0

3

6

9

12

15

18

21

# S

tory

po

ints

Team Burndown

Product Delivery Metric

Product Quality Metric

His-toric

13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43

200

400

600

800

1000

Defect trending per Sprint

CLOSING,QUESTIONS

Alex Robbio – [email protected]

Julieta Barrionuevo – [email protected]

Hubert Smits – [email protected]