• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Avantica presentacion scrum
 

Avantica presentacion scrum

on

  • 1,178 views

SCRUM training in Avantica Technologies (2010-2011)

SCRUM training in Avantica Technologies (2010-2011)

Statistics

Views

Total Views
1,178
Views on SlideShare
1,178
Embed Views
0

Actions

Likes
0
Downloads
0
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Debe conocer con quien está tratando es ingenuo llegar sin saber con quien se va a enfrentar.
  • Debe conocer con quien está tratando es ingenuo llegar sin saber con quien se va a enfrentar.
  • Debe conocer con quien está tratando es ingenuo llegar sin saber con quien se va a enfrentar.
  • Debe conocer con quien está tratando es ingenuo llegar sin saber con quien se va a enfrentar.

Avantica presentacion scrum Avantica presentacion scrum Presentation Transcript

  • AgendaWhats the software problem? Agile Agile Manifesto Origins Whats SCRUM? Used by? Used for? When to use SCRUM?
  • Agenda Roles Activities Artifacts SCRUM Rules SCRUM Add-ons How to start SCRUM SCRUM Planning SCRUM MetricsCollocation and Team Rooms
  • Whats the software problem? Releases take too long Stabilisation takes too long Changes are hard to make Quality is falling Death marches are hurting morale
  • Whats the software problem? 31.1% of IT projects will be canceled before completion 52.7% of completed projects cost on average 189% over their original estimates 16.9% of projects are completed on time and budget The larger the project, the more likely to failure Chaos Report 1995-2008
  • Whats the software problem?
  • Whats the software problem?
  • Agile
  • Agile Manifesto• Undefined (nothing “written in stone”)• Flexible (change project scope)• Visible (no late surprises)• Early results• Customer involvement (more work for client)
  • Agile Manifesto
  • SCRUM Origins• 1970: Dr. Winston Royce “Managing the development of large software systems”• 1986: Takeuchi & Nanonaka – “Hardvard Business Review”• 1990: Best practices in Japan industry (Toyota/Honda)• 1993: Jeff Sutherland – First SW development SCRUM• 1995: Ken Schwaber – SCRUM Development Process
  • Whats SCRUM?• Transparency * Inspection * Adaptation• Simplest Agile framework• Real world progress of a project = “empirical process control”• Result oriented / Value-focused• Commited-driven• Empowers and respect teams
  • Whats SCRUM?
  • Whats SCRUM?
  • Whats SCRUM?
  • Whats SCRUM? UserStories
  • Used by?
  • Used for? Commercial software  Video game development In-house development  FDA-approved, life-critical systems Contract development  Satellite-control software Financial applications  Websites ISO 9001-certified applications  Handheld software Embedded systems  Mobile phones 24x7 systems with 99.999%  Network switching applications uptime requirements  ISV applications the Joint Strike Fighter  Some of the largest applications in use
  • What can I expect?
  • When to use SCRUM?
  • SCRUM Roles Team
  • SCRUM RolesProduct Owner
  • SCRUM RolesScrum Master
  • SCRUM Activities• Time boxed meetings• Sprint is the heartbeat of the SCRUM cycle SPRINT SPRINT SPRINT DAILY PLANNING REVIEW RETROSPECTIVE SCRUM MEETING MEETING MEETING BACKLOG REFINEMENT MEETING
  • SCRUM Activities Sprint Planning• When iteration is planned• 2 hours for each week of sprint duration (8h for a 4 weeks sprint)
  • SCRUM Activities Daily SCRUM
  • SCRUM Activities Sprint Review Meeting• Not a product “demo” showtime• Inspect – Feedback – Adapt THE PRODUCT• Team present what is accomplished during the sprint• Whole world in invited
  • SCRUM Activities Spring Retrospective• Inspect – Feedback – Adapt THE PROCESS• Design a “Whats working well” - “What could work better” chart• “Start – Stop – Continue” Doing technique• Usually ignored but is A KEY for long term projects
  • SCRUM ArtifactsProduct Backlog
  • SCRUM Artifacts Sprint Backlog
  • SCRUM Artifacts Sprint Backlog
  • SCRUM Artifacts Sprint Backlog
  • SCRUM Artifacts Sprint Backlog
  • SCRUM ArtifactsBurndown Charts Sprint Burndown
  • SCRUM ArtifactsBurndown Charts
  • SCRUM ArtifactsBurndown Charts Product Burndown
  • SCRUM Rules• A potentially shippable product increment at the end of the sprint• Pottentially shippable <> Shippable• Reciprocal commitments• No changes during a sprint• Arquitecture built and user-visible functionality over time
  • SCRUM Add-ons• Optional for SCRUM approach – Release Planning – Release Sprint – Backlog Refinement – Impediment Backlog (AKA Impediment List) – Product Backlog Delta
  • How to start SCRUM?• Train the team in in the basics of SCRUM• Establish the vision• Write user stories to form the product backlog• Order the backlog items by business value• Size the backlog items• Reorder the backlog if necessary• Create the initial release plan• Plan the first sprint• Start sprinting!!!
  • SCRUM Planning?• Velocity based planning• Story points (estimate the size, not the duration)• Planning poker
  • SCRUM Metrics?• Customer and team surveys• Velocity chart• Burnup/burndown chat• Running automated test• Technical debt• Work-in-process• Story cycle time• Cost per sprint/story point• Real value delivered• ROI or NPV
  • Collocation and Team Rooms
  • Conclusions• SCRUM only attempts to manage the manageable• Not a silver bullet in project management• “Done” and “Undone” work clear for Product Owner• “Release Sprints” to complete undone work• Focus “increments” as sprint goals
  • Not the end...But to be continued, I hope :) Thanks!