scrum for developers

Post on 22-May-2015

3.522 Views

Category:

Business

1 Downloads

Preview:

Click to see full reader

DESCRIPTION

A session on what a developer needs to know when applying to a company where the PM says "we work with Scrum"

TRANSCRIPT

SCRUM FOR DEVELOPERSMohamed Ahmed MeligySenior Software EngineerSilverKey Technologies, LLCweblogs.asp.net/meligy

Project Management Methodologies

You heard about them in collage

Waterfall Model

Does it work ???

Who goes home at 5 PM ?Why did Windows Vista take 5 years ?

Every Project Story

• The customer knows nothing• The developer thinks about new technologies• The PM thinks about the deadline• The analyst thinks he knows everything

He got “everything” from the customer, who knows “nothing” ;-)

Every Project Story

• The developer: “I can do it in 3 months”• The PM: “You’ll do it in 2 months”• The project takes 4-5 month

Every Project Story

• 1st Month: Everybody is happy• 2nd Month: Customer sees “something”• 3rd Month: Customer makes tons of changes

– The developer screams– The project manager blames …. ???

• Last Month: Everybody is at office till 8-10 PM• Every DAY:

– The PM: Developer, you’re not done yet? LOSER!!

Why does it happen?

• Requirements are not fully understood at the beginning of the process.

• Requirements change during the process.• The process becomes unpredictable when

new tools and technologies are used.

Other Methodologies

• Spiral• CMMI• Rational Rose• Agile

AgileWho’s this ???

Agile Manifesto

• Individuals and interactionsOver processes and tools

• Working softwareOver comprehensive documentation

• Customer collaborationOver contract negotiation

• Responding to changeOver following a plan

Agile Methodologies

• eXtreme Programming (XP)– Pair Programming– Test Driven Development– Continuous Integration– Refactoring, Coding Standards, etc…

• Adaptive Software Development– speculate, collaborate, and learn cycles

• Scrum

SCRUM??

2-4 weeks

7-8 hours

Product BacklogAs prioritized by Product Owner

Sprint Backlog

Backlog tasksexpandedby team

Potentially ShippableProduct Increment

Daily ScrumMeeting

Source: Adapted from “Agile Software Development with Scrum” by Ken Schwaber and Mike Beedle.

Scrum Model

Prerequisites

• Small Team• Good People• Common Sense

Product BacklogList of work items during the entire project

SprintA certain period of time with specific deliverables

Lasts for 2-4 weeks – NO MORE NO LESS

Sprint

• Before Start: Sprint Planning• Starts with Sprint Backlog

Choose highest priority items remaining in product backlog

• Ends with Deliverables– New Features Developed / Old Bugs Fixed– Sprint Zero and Sprint One might deliver documents!

• Architecture Documents• UI Prototype

• After End: Sprint Review Usually just before next sprint planning

Sprint Daily Meetings

What did you do Yesterday ?What will you do today ?

Do you have any problems ?

Sprint Daily Meetings

• Stand up Meetings• 15 Minutes Max.

– Well, don’t exceed 30 minutes at least

• Entire Team

Scrum Roles

Product OwnerScrum MasterProject Team

Scrum Roles: Product Owner

• Possibly a Product Manager or Project Sponsor– That’s what we call an “analyst”

• Marketing• Internal Customer• etc.

– Not a technical guy, BUT ….

Scrum Roles: Scrum Master

• Responsible for enacting Scrum values and practices– Manages the sprint meeting– Does the sprint reporting

• Typically a Project Manager or Team Leader– That’s what the books say– I have played it a different way

Scrum Roles: Project Team

• Cross-functional– QA– Developers– UI Designers– etc

• 5-10 members (as the books say)– I’d rather 5 to 7 MAX per team

Scrum Artifacts

Product BacklogSprint Backlog

Burndown Chart

Burndown Chart

SCRUM AND YOUThe Developer

Self Management

50% for managing yourself25% for managing your boss

25% for managing everybody else

(Dee Hock – Founder of VISA)

Accept Flexible Deliverables

As this means flexible scheduleTry not to hate the customer :-D

Be ReliableYou are a good guy / gal ;-)

Common Sense

Be ReliableYou’ll make mistakes

APOLOGIZE

Take CareYou have your good day and bad day

You have your productive and your slow weeks

Take CareDo NOT extend a sprint period

Do I have the choice??

The Real World

Reality has a tendency to make a beautiful project plan ugly

Problems!There’s no silver bullet

Where to go

• www.controlchaos.com• www.scrumalliance.org

• My weblogweblogs.asp.net/meligy

Ken Schwaber, 2004ISBN 073561993X

top related