ESEconf2011 - Caine Matthew: "Creating an Environment of Teamwork, Quality, Innovation and Fun"


Published on

Published in: Technology
  • Be the first to comment

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

No notes for slide
  • Is this a familiar story to you?
  • Would you feel quite so proud now?
  • Is this possible?Do you doubt it?
  • Anyone know why a software house with multiple clients all ‘shouting’ loudest needs a little more than Scrum offers?
  • Just take a moment… read these. Any of the new to you?
  • It involves Product Managers, Business Analysts, Developers, Testers, Supporters and of course the management.Believe me, slackers were quickly identified!People who complete their work do help others that are overloaded.
  • Really helps with UI and complex calculations.Test as soon as the developer checks-in (should really test before check-in!)
  • It is important to realise that you cannot close the gap overnight. It takes time.Continuous improvement is what is needed.
  • Better than a larger organisation!New clients create buzz and even more motivation!
  • And Fun is what we all want!What can be better than that.
  • ESEconf2011 - Caine Matthew: "Creating an Environment of Teamwork, Quality, Innovation and Fun"

    1. 1. Creating an Environment fullof Teamwork, Innovation, Quality and Fun<br />Matthew Caine, Infonic AG<br />
    2. 2. We Start with a Great Story<br />Going back in time…<br />… at 4am I know where René was, but where were you?<br />
    3. 3. We delivered!<br />The delivery worked!<br />The client was happy!<br />Fantastic… life does not get much better!<br />Really a Great Story!<br />
    4. 4. Was it “Really” a Great Story?<br />Delivered at the 3rd attempt<br />6 months late<br />At the expense of another client<br />Clients not reference-able<br />Lost revenue<br />Less profitable<br />Less bonus for all<br />Finally … René’s wife, daughters and<br />two dogs were not seen for two weeks.<br />
    5. 5. The next 18 months resulted in every subsequent release being delivered:<br /><ul><li>On time
    6. 6. In scope
    7. 7. In budget
    8. 8. With ever better quality</li></ul>Resulting in Teamwork, Quality, Innovation and of course, FUN! We shall prove it too!<br />Now for a truly Epic Story<br />
    9. 9. How did we do it?<br />
    10. 10. How did we do it?<br />With the exception of the fifth point, nothing above is new,<br />but it is how it all comes together, which is key.<br />
    11. 11. Adopting an Agile Methodology (DSDM Atern)<br />Operational Improvement #1<br />
    12. 12. Adopting an Agile Methodology<br />First, why DSDM Atern and not SCRUM?<br />
    13. 13. Adopting an Agile Methodology<br />First, why DSDM Atern and not SCRUM?<br />Demand Funnel<br />Scrum World<br />DSDM World<br />
    14. 14. The 8 Principals of DSDM Atern<br />
    15. 15. Convince senior management<br />Awareness training for all staff member<br />Practitioner’s course for key staff and team leaders<br />Create the Prioritized Requirements List (PRL) for a release<br />Let the team estimate and plan the time-boxes<br />Use a tool such as Jira - Put the PRL into it<br />Start development of the release, following the 8 principals<br />Review progress after 6 months<br />Real-Life Roll-Out<br />“Plus some good old-fashioned hard work!”<br />
    16. 16. Insistence that the entire team contribute to effort estimation<br />Operational Improvement #2<br />
    17. 17. The Problem is Not What You Think<br />We all know that the people doing the work must provide the estimates. Promote this!<br />However the real issue lies elsewhere… but where?<br />
    18. 18. The Problem is Not What You Think<br />We all know that the people doing the work must provide the estimates. Promote this!<br />However the real issue lies elsewhere… but where?<br />Management! They are part of the team!<br />
    19. 19. The Problem is Not What You Think<br />e.g. 1 When a new client is won, if 30% of the requirements are unclear, then during negotiations it must be made clear that these will require in-depth analysis prior to making any commitment.<br />e.g. 2 If a team estimates 40 days for a feature based on high-level requirements, don’t shoot the team when the exploration results in 100 days… don’t force them to do it in 40.<br />BE PART OF THE TEAM – PROVIDE SUPPORT.DON’T DICTATE “THE WHAT” AND “BY WHEN”!<br />
    20. 20. Dedicate the whole company to testing at key times<br />Operational Improvement #3<br />
    21. 21. “It must be their environment”<br />“The software works, I tested it myself”<br />“Testers don’t know the business”<br />“I don’t write software with bugs in”<br />“Just ship the software, it’ll be ok”<br />“The test case is wrong, I’ll fix the test case to fit the software”<br />The Quality Attitude – No Teamwork<br />
    22. 22. Quality is not just Attitude<br />A software product house also has to address these:<br /><ul><li>Regression test the full product
    23. 23. Efficiently remove the back-log of defects that will have built up over the years
    24. 24. Align key resources to fix client UAT issues post release
    25. 25. Provide reasonable time for teams to plan
    26. 26. Improve infrastructure for build effectiveness</li></li></ul><li>Focus Quality within Timeboxes<br />3<br />4<br />5<br />6<br />2<br />1<br />An Agile methodology will introduce Time Boxes:<br /><ul><li>A Timebox lasts 2-6 weeks (we use 3 weeks)
    27. 27. A release consists of a number of timeboxes
    28. 28. Here we see a release consisting of 6 time boxes, or 18 weeks.</li></li></ul><li>Focus Quality within Timeboxes<br />2<br />3<br />4<br />Regr.<br />1<br />Quality<br />We action was to introduce two special Timeboxes:<br /><ul><li>Quality at the start
    29. 29. Regression at the End</li></li></ul><li>The Quality Time Box<br />This is all high interrupt work that should be avoided when focusing on new development<br />
    30. 30. The Regression Testing Time Box<br />The whole company tests, all coordinated by the QC team – it is oneproduct, our product.<br />During this, we have seen real teamwork and inter-team work:<br /><ul><li>Team members helping each other out
    31. 31. Teams helping each other
    32. 32. High commitment to get the release out of the door</li></li></ul><li>The Results are Quantifiable<br />Just regression testing is not enough…<br />... combining regression & quality time-boxes provides the “leap”<br />
    33. 33. Improve width and depth of automated testing<br />Operational Improvement #4<br />
    34. 34. When a new product is developed, test automation keeps pace.<br />However, developers are usually added to the team before testers.<br />Now, automation can no longer maintain coverage at the same pace that new functionality is delivered.<br />A gap appears and continues to grow.<br />Consequences are obvious!<br />Mind the Gap<br />
    35. 35. Close the Gap<br />Use the MoSCoW prioritization mechanism introduced by the Agile methodology to prioritize the Regression testing time box.<br />Remember DSDM Atern Principal # 4?<br />“Never compromise on quality”.<br />
    36. 36. Actual Progress of Gap Closure<br />
    37. 37. Final Release Quality is Measureable<br />One FTSE-100 company:<br /><ul><li>Approx. 75% reduction in UAT critical issues.
    38. 38. Quality being sustained.
    39. 39. Client is not just happy, but “ecstatic” about the quality.
    40. 40. The client could now cover more tests!</li></li></ul><li>Merge Support and Quality Control teams<br />Operational Improvement #5<br />
    41. 41. Lots of Pain for Support & QC<br />
    42. 42. Merge them: Wow!<br />
    43. 43. Bringing it all Together<br />Summary<br />
    44. 44. Teamwork & Quality are...<br />
    45. 45. Examples include:<br /><ul><li>New User-Interaction Model (RIA) with Adobe Flex.
    46. 46. 3-Tier architecture
    47. 47. A Cube data access mechanism for easier reporting</li></ul>Plus, because due diligence reports have been excellent, we are also building new functionality required by new clients.<br />… the Key to Innovation…<br />
    48. 48. … which Creates a Fun Environment!<br />
    49. 49. Any Questions?<br />Ah yes before I forget, René does now get to see his wife and two daughters. Plus his two dogs now get regular morning walks!<br />
    50. 50. Leads Infonic’s Operational Control function, where he is responsible for software release management, business process management, and management information systems. Mr. Caine brings 18 years of experience in the financial services IT sector, offering project management experience, business analysis and software development and delivery expertise.<br />Prior to joining Infonic, Mr. Caine served as a People Manager, Head of Operating and Monitoring at Avaloq, a Swiss core-banking solutions provider based in Zürich, where he specialized in product management and operations, and led multiple teams of analysts and developers. He also served as Vice President, Business Analysis in Swiss Re’s global asset management division, where his role involved business analysis, testing and support.<br />His prior position was as Senior Consultant in the Finance practice at Logica Consulting, an IT and business services company, based in London, Zürich, Berlin and Geneva, where he focused on software development. Mr. Caine holds a Bachelors of Science degree, with Honors, in Computer Science from the University of Staffordshire in England.<br />Aboutthe Speaker - Matthew Caine<br />