ITCamp 2012 - Dan Nicola - Scrum v2
Upcoming SlideShare
Loading in...5

ITCamp 2012 - Dan Nicola - Scrum v2






Total Views
Slideshare-icon Views on SlideShare
Embed Views



0 Embeds 0

No embeds



Upload Details

Uploaded via as Adobe PDF

Usage Rights

CC Attribution-NonCommercial-ShareAlike LicenseCC Attribution-NonCommercial-ShareAlike LicenseCC Attribution-NonCommercial-ShareAlike License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

    ITCamp 2012 - Dan Nicola - Scrum v2 ITCamp 2012 - Dan Nicola - Scrum v2 Presentation Transcript

    • Architecture &ITCamp 2012 sponsors Best Practices@ itcampro # itcamp12 Premium conference on Microsoft technologies
    • SCRUM. Removing ImpedimentsDan Nicola | MAXCODE
    • What to expectAgile principles & ScrumTop 7 impedimentsHow good is your Scrum?
    • Individuals and interactions over processes and tools
    • Working software overcomprehensive documentation
    • Customer collaboration over contract negotiation
    • Responding to change over following a plan
    • Scrum Framework3 roles3 artifacts5 ceremonies
    • 3 rolesProduct OwnerScrum MasterTeam
    • 3 artifacts
    • 5 ceremoniesProduct GroomingSprint PlanningDaily MeetingSprint ReviewSprint Retrospective
    • ImpedimentsKeep the team from being productiveTeam – communicateScrumMaster - remove
    • Lack of focus
    • No working software (not DONE)
    • Priorities and specifications (backlog issues)
    • Waterfall mindset
    • Interruptions
    • Technical debt
    • Dependency on key people
    • Removing impediments… …makes the difference!
    • Remember! Let the team do the work Rapid value creation is key! SCRUM makes it work, The Team does the work SM enables the process Protects, facilitates and coaches Ensures impediments are busted
    • ScrumBut...(ScrumBut)(Reason)(Workaround)
    • ScrumBut... TestAka the “Nokia Test”Goals:  Indicator where you are in your Scrum practices  Collect data for a statistical study9 Questions
    • QuestionsIterationsTestingAgile SpecificationsProduct OwnerProduct BacklogEstimatesSprint Burndown ChartTeam DisruptionsTeam
    • Questions Fixed iteration length 4 weeks or less Software is deployed Good user stories tied to specifications as needed Product Owner who motivates team Product Owner can measure ROI Estimates produced by planning poker by team Burndown chart burns down when story is done Noone disrupting team, only Scrum roles Team is in hyperproductive state
    • Scrum SmellsLoss of RhythmTalking ChickensMissing PigsPersistent SignaturesScrum Master Assigns WorkThe Daily Scrum is for the Scrum MasterSpecialized Job RolesSource: “Toward a Catalogue of Scrum Smells”, by MikeCohn
    • ConclusionScrum is not going to solve your problems,it’s just going to make them in-your-faceobvious, every day. (Ken Schwaber)
    • Thank You! I’d really appreciate your feedback! DAN.NICOLA@MAXCODE.RO@ itcampro # itcamp12 Premium conference on Microsoft technologies