Download presentation
Presentation is loading. Please wait.
Published byJunior Banks Modified over 9 years ago
1
A Transition to Scrum Introduction Presented by Sylvain Jean, CSM © 2011 Révolution Agile. All rights reserved. www.revolutionagile.ca
2
Initial Situation Controlling and directive micro management (« Plan- driven »). Obvious gap between system analysts, coders and testers (not focussing on the same thing at the same time). Poor product quality… Search for the culprits Everyone is on the defensive! Wide-spread demotivation: PLM unsatisfied DEV pride shaken QA impatience and misunderstanding. Efforts made to develop functions that do not match customer needs at the time of delivery. A lot of developed features stay on the shelves. Inability to deliver a product from the "Trunk“ source code base.
3
Goals and Objectives Improve quality of delivered products More frequent delivery Delivery to meet customer needs (flexibility and adaptability) Boost motivation and commitment
4
Scrum and Agile Scrum and Agile can resolve most of the problems we are facing in the domain of software engineering and product delivery. True or False? False! Problems are resolved by people. Scrum and Agile provide tools to expose problems and to mobilize the whole team toward their resolution.
5
Agile Values Collaboration Commitment Communication Courage Enjoyment Feedback Focus Learning Openness Quality Respect Simplicity
6
Agile Ingredients Scrum Teams Product Backlog Iterations Project Management Software Development Practices Relational Practices Review and Retrospective Change Management The Three pillars of Scrum: Transparency, Inspection and Adaptation
7
Project Management Triangle
8
Results GoalResult Product Quality Release Frequency Meet customer needs Motivation and commitment Other considerations Mixed results in respect to the assent of senior management and other groups within the company. Difficult for the team to thrive to reach the next level of improvement (requires a lot of effort and courage). Need to resolve how to properly coordinate maintenance work and release development. Achieved
9
References Mon blog http://lecoinagile.blogspot.com/ Control Chaos Web Site by Ken Schwaber - Advanced Development Methods, Inc. http://www.controlchaos.com/ Agile Retrospectives - Making Good Team Great By Esther Derby and Diana Larsen http://www.scribd.com/doc/13380708/Agil eretrospectives Agile Estimating and Planning Mike Cohn User Stories Applied Mike Cohn Working Effectively with Legacy Code By Michael Feathers (2004) Forming, storming, norming and performing - Tuckman's Group Development Model From Wikipedia, the free encyclopedia http://en.wikipedia.org/wiki/Forming,_storming,_n orming_and_performing RAPID Development Steve McConnell Agile Software Development with Scrum Ken Schwaber, Mike Beedle The Enterprise and Scrum Ken Schwaber revolutionagile.ca © 2011 Révolution Agile. Tous droits réservés.
10
Thank you! sjean@revolutionagile.ca www.revolutionagile.ca lecoinagile.blogspot.com Révolution Agile
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.