View stunning SlideShares in full-screen with the new iOS app!Introducing SlideShare for AndroidExplore all your favorite topics in the SlideShare appGet the SlideShare app to Save for Later — even offline
View stunning SlideShares in full-screen with the new Android app!View stunning SlideShares in full-screen with the new iOS app!
Source Standish GroupHere are the success rates of ITprojects in 2009.Succeeded38%Failed33%Stopped29%
Source Standish GroupThese rates are still better thanin 1994.Succeeded16%Failed52%Stopped31%
Source Standish Group1. Lack of Change Management2. Poor Communications3. Inadequate Resources4. Poorly Defined Requirements5. Inaccurate Estimates6. Poor Risk Management7. Poorly Defined Deliverables8. Over Optimism9. No Time for Project Management10. Technical IncompetenceWhy do projects fail ?
Value OverTeamSoftwareCollaborationChangeHere comes the AgileManifesto.Individuals and interactionsWorking softwareCustomer collaborationResponding to changeProcesses and toolsComprehensivedocumentationContract negociationFollowing a plan
An Agile methodology is a setof practices using Agileprinciples as core values.
1. Customer satisfaction by rapid delivery of useful software2. Welcome changing requirements, even late in development3. Working software is delivered frequently (weeks rather than months)4. Working software is the principal measure of progress5. Sustainable development, able to maintain a constant pace6. Close, daily cooperation between business people and developers7. Face-to-face conversation is the best form of communication (co-location)8. Projects are built around motivated individuals, who should be trusted9. Continuous attention to technical excellence and good design10. Simplicity—the art of maximizing the amount of work not done—is essential11. Self-organizing teams12. Regular adaptation to changing circumstances
XP, RAD, Scrum & Kanban are someAgile methodologies or Agileimprovement methods.
RequirementSpecificationDesignImplementationUnit TestingValidationUser testingTimelineLets have a look on theV-Model.
Maybe you are wondering whatis the role of the Scrum Master ?
SHU守HA破RI離SM sets up the process, helpsthe team get to a sustainablepace with known velocity anduses the Retrospective tointroduce change thatimproves velocity.SM has a team that getssoftware done at the end ofthe sprint and has a goodproduct owner with readybacklog at the beginning of asprint. The team is positionedto work on hyperproductivity,the design goal of Scrum.SM is needed but dont have todo much.
ValueQualitySpeedQuickly buildrobust anduseless featuresBuild robust and useful features thatare not needed anymoreBuild usefulfeatures "quick &dirty"
Sprint burndown allows thefollow the sprint activity.FeaturesTimelineSprint durationSprintbacklogPerfect lineReal team lineSomething is wrong : adapt sprintduration or velocity
Burndown can be extendedto the whole project.FeaturesTimelineInitial project durationProductbacklogPerfect lineReal team line : 2 more sprintsthat originally planned areneeded.Something is wrong inthe projectSprints
Burnup charts shows thebusiness value of the project.ValueTimelineProductbacklogPerfect lineSprintsSomething is wrong :review prioritization andsprint planning.Real time line