Generali Agile Tour Luxembourg 2009 En


Published on

Published in: Business, Technology
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Generali Agile Tour Luxembourg 2009 En

  1. 1. Get on board with SCRUM… Yann GENSOLLEN GENERALI – Direction INTERNET
  2. 2. <ul><li>Introduction </li></ul>
  3. 3. Why did the Internet Department of genrali chose Scrum for managing IT Projects ? <ul><li>Agile modeling improves Project Management </li></ul><ul><li>Agile modeling is used in IT development to : </li></ul><ul><ul><li>Involve the client in the project, allowing us to increase our reactivity </li></ul></ul><ul><ul><li>Be more pragmatic than with traditional methods </li></ul></ul><ul><ul><li>Completely meet our client’s requirements </li></ul></ul>
  4. 4. Why did the Internet Department of genrali chose Scrum for managing IT Projects ? <ul><li>A background explanation of why we chose Scrum : </li></ul><ul><ul><li>Our goal was to release its on-line insurance web site ‘’ 5 month after the Internet Department was created </li></ul></ul><ul><ul><ul><li>High benefit and stake project </li></ul></ul></ul><ul><ul><ul><li>Strong support from Managing staff </li></ul></ul></ul><ul><ul><ul><li>Very active sponsor </li></ul></ul></ul><ul><ul><ul><li>Very short deadlines </li></ul></ul></ul><ul><ul><li>Our goal was also to choose a method that would allow us to : </li></ul></ul><ul><ul><ul><li>Release a first version of the website within a very short period of time </li></ul></ul></ul><ul><ul><ul><li>Release the first version very rapidly with regular new releases </li></ul></ul></ul>
  5. 5. Well-identified roles within each project Product Owner Maitrise d’ouvrage Maitrise d’œuvre Scrummaster Scrum team
  6. 6. Well-identified roles within each project <ul><li>Product Owner = ship owner </li></ul><ul><ul><li>Determines the destination and content of the software release and every iteration </li></ul></ul><ul><ul><li>Can readjust the scope of action before every iteration </li></ul></ul><ul><li>Scrummaster = captain </li></ul><ul><ul><li>He is the only one in charge </li></ul></ul><ul><ul><li>He must prevent the team from any scope change during an iteration </li></ul></ul><ul><ul><li>He is responsible for informing and deciding not to start a new iteration if the scope determined by the PO is not acheivable </li></ul></ul><ul><ul><li>Project release = stopovers </li></ul></ul><ul><ul><li>At the end of every iteration, the team presents the result of its work to the PO during a sprint review </li></ul></ul><ul><ul><li>During the sprint review the PO can readjust his demand in the light what has been achieved and of any new elements affecting the project </li></ul></ul>Source : Christophe LEONARD - GENERALI
  7. 7. Scrum methodology benefits <ul><li>Advantages </li></ul><ul><li>By focusing the team on regular achievable goals, Scrum allows to : </li></ul><ul><ul><ul><li>Improve the team’s productivity, compared to other methods </li></ul></ul></ul><ul><ul><ul><li>Refocuses the project on the team members, it’s creativity </li></ul></ul></ul><ul><ul><ul><li>Places the customer back in the heart of the project therefore allowingproduct adjustmentsat the end of every sprint </li></ul></ul></ul><ul><ul><ul><li>Every sprint measures the team’s velocity (number of points that the team is able to achieve in one sprint) and gives a more reliable tate of achievement for the whole project </li></ul></ul></ul>
  8. 8. What we have learned from experience <ul><li>After one and a half year using Scrum, our advice is to : </li></ul><ul><ul><ul><li>Ask for the help of scrum experienced teams operational users and IT management </li></ul></ul></ul><ul><ul><ul><li>Carefully prepare the preliminary phase (Sprint 0) </li></ul></ul></ul><ul><ul><ul><li>Have a full product backlog ready for the first release </li></ul></ul></ul><ul><ul><ul><li>Set up a continuous integration and automatic testing </li></ul></ul></ul><ul><ul><ul><li>Appoint someone who will be responsible for checking compliances </li></ul></ul></ul><ul><ul><ul><li>Start methodology implementation on project with limited compliances </li></ul></ul></ul><ul><ul><ul><li>Be carefull with writing the working documents </li></ul></ul></ul>
  9. 9. What we have learned from experience <ul><li>Team relations </li></ul><ul><ul><ul><li>Better communication and understanding within the team, confidence and team involvement </li></ul></ul></ul><ul><ul><li>Project management </li></ul></ul><ul><ul><ul><li>Comprehension of the priorities and a better flexibility </li></ul></ul></ul><ul><ul><ul><li>Shares responsibilities, alerts and facilitates decisions </li></ul></ul></ul><ul><ul><ul><li>Better project completion visibility through ‘sprint’ reviews </li></ul></ul></ul><ul><ul><ul><li>Cost efficiency control through functional adjustments </li></ul></ul></ul><ul><li>Developments and deadlines </li></ul><ul><ul><ul><li>Features optimization, developments accuracy, shorten life-cycles </li></ul></ul></ul><ul><ul><ul><li>Capitalization / Optimization of the product after each ‘sprint’ </li></ul></ul></ul><ul><li>Project visibility </li></ul><ul><ul><ul><li>Good management and other actors reporting and visibility through ‘sprint’ reviews </li></ul></ul></ul><ul><ul><ul><li>Emphasize team individuals </li></ul></ul></ul>
  10. 10. Any questions ? Any questions ?