2. Who I’m? (IT)manager (trained and by parctice) Sergant (Border guard) Store Manager Sales and Branch Manager Project Manager Infrastructure and outsourcing Manager Development Manager IT/IS Department Manager Wife and 4 kids At the moment: Trainer/mentor (Scrum and Agile) Scrum.ee founder CSM, CSPO, CSP www.linkedin.com/in/alekkozlov 2 Alek Kozlov +372 5021033 alek@scrum.ee
3. The facts about IT development The Standish Group has studied over 40,000 projects: 3 Alek Kozlov +372 5021033 alek@scrum.ee IT project success rate 1994: 15% IT project success rate 2004: 34% http://www.softwaremag.com/L.cfm?Doc=newsletter/2004-01-15/Standish http://www.flickr.com/photos/kattebelletje/3330981541/
4. “What’s happening?” Often Sometimes 64 % !!!! Never Source: Standish Group Study Reported at XP2002 by Jim Johnson, Chairman http://www.flickr.com/photos/hugovk/3518305854/ 4 Alek Kozlov +372 5021033 alek@scrum.ee
5. Factors inpacting project sucess Success possibility Appropriate actions 20% 80% Tight control and other influence methods 80% Right partner Dedication and cooperation Supporting system 20% 5 Alek Kozlov +372 5021033 alek@scrum.ee ... Order quality Product vision
6. Today we will discuss... 6 Alek Kozlov +372 5021033 alek@scrum.ee Dedication and cooperation Order quality Supporting system Product vision
7. Product Vision OR How to manage the MIST? Product vision http://www.flickr.com/photos/seabamirum/2926154653/ 7 Alek Kozlov +372 5021033 alek@scrum.ee
9. Product Vision Good Product Owner is responsible for establishing a shared vision statement Best Product Owners work out the vision statement with the stakeholders (team is also stakeholder!!!) Best Product Owner helps the team to remember the original vision and to stay on the right way when somebody want to do something “very cool”. Alek Kozlov +372 5021033 alek@scrum.ee 9
10. How to manage mist? ... or the tools for establishing shared vision: “Product box” (3-5 main selling points for your product) “Looking from the future” Press release Elevator statement Alek Kozlov +372 5021033 alek@scrum.ee 10
11. Supporting System 11 Alek Kozlov +372 5021033 alek@scrum.ee support system - a network of facilities and people who interact and remain in informal communication for mutual assistance; a network that enables you to live in a certain style(http://wordnetweb.princeton.edu) Support System: The collection or assembly of support devices arranged to provide complete support for the home when installed for human habitation. (http://earthquakeadvisor.com/documents/mobilehomes/emhssd/2.html) Dedication and cooperation Order quality Supporting system Product vision
12. Supporting systems Technical infrastructure Training Administration (obstacle management) Law infrastructure And everything else that supports our work on product 12 Alek Kozlov +372 5021033 alek@scrum.ee
13. Supporting system 13 Alek Kozlov +372 5021033 alek@scrum.ee Agreed rules, processes, arrangements should be stated in written document (agreement). WHY? Company policy, stating that written agreement is a must (and we should respect that) We tend to forget things and it brings us to conflicts that could undermine our cooperation and the project success!
14. Example of frame agreement (1) Definitions 1. Applicability of the Agreement 1.1 This agreement stipulates the general terms to applied to the co-operation of the Parties and to separate Projects carried out between Customer and the Supplier 2. General Obligations of the Parties 3. Administration for the Co-operation: Partner Managers 14 Alek Kozlov +372 5021033 alek@scrum.ee
15. Example of frame agreement (2) 4. Project Orders 5. Administration of Projects 6. Change Orders 7. Acceptance of Deliverables 7.1 “Test Period”. For example: If the Project is less than x weeks, the Test Period shall be 5 days. If the Project is x weeks or more, the Test Period shall be 10 days. 15 Alek Kozlov +372 5021033 alek@scrum.ee
16. Example of frame agreement (3) 8. Subcontracting 9. Delay 10. Payment of the price of the Project The price of the Project will be invoiced by the Supplier after the final Product has been accepted by Customer 16 Alek Kozlov +372 5021033 alek@scrum.ee
17. Example of frame agreement (4) 11.Site Inspections 12. Warranties 13. Third Party Products 14. Intellectual Property Rights 15. Intellectual Property Rights Indemnification 15.1 The Supplier represents and warrants that it has a right to grant Customer rights set forth in Section 14 and that this does not in any way violate the rights of third parties… 16. Secrecy 17. Termination of a Project 18. Term and Termination of this Agreement 19. Final provisions Appendix [x]: Project Order 17 Alek Kozlov +372 5021033 alek@scrum.ee
18. Order Quality Well-formed User Stories Right amount of User Stories should be given to the team 18 Alek Kozlov +372 5021033 alek@scrum.ee Dedication and cooperation Order quality Supporting system Product vision
19. Some User Story tools to catch, form, organise, and prioritise: Story-writing workshops INVEST (Independent, Negotiable, Valuable, Estimatable, Sized Appropriately, Testable) KANO analyses Mandatory Linear Exciters/Delighter (Nice to have) “Buy the feature” Alek Kozlov +372 5021033 alek@scrum.ee 19
20. Software process cycle ... Begins and ends with the customer Cycle Time Product Starts Delivering Product Concept Value Cycle Time Feature in Production Feature Request Maintenance Patch Deployed Cycle Time Urgent Need Source: Mary Poppendieck 20 Alek Kozlov +372 5021033 alek@scrum.ee
23. Amount of work done depends on team velocity “How to be more effective?” Realise what is behind your team velocity Together with Scrum Master and the team remove impediments to increase team velocity Alek Kozlov +372 5021033 alek@scrum.ee 23 Team Velocity Team velocity
24. How to reduce cycle time Even out the arrival of work Minimize the number of things in process Minimize the size of things in process Establish a regular cadence Limit work to capacity Use pull scheduling Alek Kozlov +372 5021033 alek@scrum.ee 24 Source: Henrik Kniberg; Introduction to Lean
25. Dedication and cooperation Dedication Cooperation 25 Alek Kozlov +372 5021033 alek@scrum.ee Dedication and cooperation Order quality Supporting system Product vision
26. Product Owner characteristics Understands the market, customers and users Has a vision and can communicate the vision Has good working relationship with stakeholders Empowered to make decisions, is decisive, is willing to say no Leader and facilitator Alek Kozlov +372 5021033 alek@scrum.ee 26 Source: Mike Cohn
27. So, who is the Product Owner? http://www.flickr.com/photos/scott_schmitz/527182264/ http://www.flickr.com/photos/eraphotos/2979677983/ 27 Alek Kozlov +372 5021033 alek@scrum.ee
28. Good product owner first of all... ...concrete, provide directions, is decisive, is willing to say no and controls the results? ... helping others to achieve in their movements harmony, unity and unison? YES NO http://www.flickr.com/photos/eraphotos/2979677983/ 28 Alek Kozlov +372 5021033 alek@scrum.ee
29. Cooperation, cooperation and one more time cooperation Cooperation, and cooperation, and again cooperation, and always cooperation, and COOPERATION WHY? http://www.flickr.com/photos/scott_schmitz/ We are in the one boat! If we win, that is only together!If we lose – also together! 29 Alek Kozlov +372 5021033 alek@scrum.ee
34. Agile product managment experience Ministry of Finance of Estonia – information system for managment of European Structural Funds aids – SFOS, SFCS(BI), Enterprise Service Bus Baltika AS – large Estonian manufacturer and retailer (7 countries; Brands: Baltman, Monton, Mosaic, Ivo Nikkolo) – ERP, Business Intelligence 34 Alek Kozlov +372 5021033 alek@scrum.ee