Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Kupe – PM and 
Governance 
Agile Connect 
FishServe, Wellington, 21 November 2014 
John Tucker, FishServe 
Mark Jones, FIN...
Agenda 
• Intro to FishServe and FINNZ 
• Intro to the Kupe Project 
• Starting Kupe 
• Running an Agile Project 
• Benefi...
FishServe 
• Operate in a statutory environment 
• Previously part of MPI (government) – now an industry 
owned private co...
Registry Services 
• Quota and Annual Catch Entitlement (ACE) trading and 
allocation 
• Issuing Fishing Permits and Fishi...
FishServe 
• Registry Services Provider – as required under the Quota 
Management System 
• Capture, Validate, Host, and S...
• Wholly Owned Subsidiary of FishServe – Business 
Development Company 
• Leveraged Fisheries experience, applied in wider...
Fisheries Management System (FMS) 
• FMS core software – Owned and Paid for by Industry, data 
held belongs to MPI 
• Firs...
Driver for Change 
• Evolving Industry needs and business development opportunities 
• Vision to be continued sole supplie...
Kupe Project Goals 
Kupe Project established to provide a software platform to 
support statutory vision and goals: 
• The...
Starting the Kupe Project 
• Documented system High Level Requirements 
• Feature estimates, Design, Dev and Test 
• Detai...
Agile expected benefits 
• “Cost of code” 
• Better alignment with business needs 
• Better visibility to project 
• Stop ...
Selling Agile 
• Steering Committee 
• Project sponsor experience as Director of NAIT 
• Over whelming support for change ...
• Agile Coach: Pete Tansey, Petoni Mahi Limited 
• Architect: Col Perks, Tenzing Ltd 
• TDD & BDD Training: Rob Maher, Rob...
Reporting 
• FishServe Board – simple burn up 
• Story points 
• Budget 
• Reporting to steering committee after each spri...
• MoSCoW 
Scope Management 
• Definition of Priorities 
• Perhaps better to change names 
• Now/not now 
• Discuss what bo...
Starting the Kupe Project 
Note: Contains dummy data to illustrate points.
Completion Heatmap 
Note: Contains dummy data to illustrate points.
Cost Heatmap 
Note: Contains dummy data to illustrate points.
Lessons Learned 
• Scrum does not equal Agile 
• Early information is double edged 
• Establish governance structure early...
Questions?
Upcoming SlideShare
Loading in …5
×

Agile Project Management and Governance

835 views

Published on

Presentation to Agile Connect, Wellington, 21 Nov 2014.

Starting in early 2014, FINNZ has been working with FishServe on the ‘Kupe’ project, which has implemented an Agile methodology as the means to deliver the new Fisheries Management Solution for NZ’s Commercial Fishing Industry.

The presentation gave insight to the project management and governance challenges and practices that FishServe and FINNZ have experienced and how we have successfully overcome them as we progress through this project journey.

If you are looking to use an Agile methodology in your next project, please feel free to contact us for help or friendly advice. www.finnz.com

Published in: Software
  • Be the first to comment

Agile Project Management and Governance

  1. 1. Kupe – PM and Governance Agile Connect FishServe, Wellington, 21 November 2014 John Tucker, FishServe Mark Jones, FINNZ
  2. 2. Agenda • Intro to FishServe and FINNZ • Intro to the Kupe Project • Starting Kupe • Running an Agile Project • Benefits Realisation • How are we Operating now? • Questions
  3. 3. FishServe • Operate in a statutory environment • Previously part of MPI (government) – now an industry owned private company • Operate under two service delivery models; • Delivery on behalf of MPI to Industry (contracted) • Delivery on behalf of Industry to Industry (devolved)
  4. 4. Registry Services • Quota and Annual Catch Entitlement (ACE) trading and allocation • Issuing Fishing Permits and Fishing Vessel Licenses • Balancing Catch against entitlements • Processing catch data (logbooks) • Information collected through the services provided underpins the management of NZ fisheries
  5. 5. FishServe • Registry Services Provider – as required under the Quota Management System • Capture, Validate, Host, and Share Fisheries Data. • We are administrators – ensure that fisheries data is ready for use by Fisheries Managers, Scientists, Enforcement Officers and Fishers.
  6. 6. • Wholly Owned Subsidiary of FishServe – Business Development Company • Leveraged Fisheries experience, applied in wider Environment, Natural Resources and Heritage Sectors • Government agencies – NZ, Australia and Middle East • Give effect to policy through consultancy, requirements analysis, software, operations.
  7. 7. Fisheries Management System (FMS) • FMS core software – Owned and Paid for by Industry, data held belongs to MPI • First developed in 2001 to support wholesale legislative change to Quota Management System • Since introduction it has had 2 .Net upgrades • 400 plus screens, Web front end, Integration to finance systems and third party fishing software, plus data exchange with MPI.
  8. 8. Driver for Change • Evolving Industry needs and business development opportunities • Vision to be continued sole supplier of services to industry’ • We will use technology to ensure we are flexible, responsive and cost effective in delivering services • We will build a culture which encourages innovation, welcomes changes and minimises bureaucracy and hierarchy
  9. 9. Kupe Project Goals Kupe Project established to provide a software platform to support statutory vision and goals: • The system must achieve 100% compliance with the Law and service delivery contracts • The system must allow flexibility to provide a layer of management by industry beyond that required by Law • The system should be reusable as a generic platform for other registry services • The system should be a marketable product for FINNZ
  10. 10. Starting the Kupe Project • Documented system High Level Requirements • Feature estimates, Design, Dev and Test • Detailed budget, including resource utilisation and external parties • Third party project review • Business case submitted to FishServe’s Board for approval
  11. 11. Agile expected benefits • “Cost of code” • Better alignment with business needs • Better visibility to project • Stop any time
  12. 12. Selling Agile • Steering Committee • Project sponsor experience as Director of NAIT • Over whelming support for change • Kupe project team • More positive, but still hesitant • Commitment by Governance group • including training/support
  13. 13. • Agile Coach: Pete Tansey, Petoni Mahi Limited • Architect: Col Perks, Tenzing Ltd • TDD & BDD Training: Rob Maher, Rob Maher Consulting • UX: Touchcast Starting Agile
  14. 14. Reporting • FishServe Board – simple burn up • Story points • Budget • Reporting to steering committee after each sprint • Detailed sprint progress, and “short” burnup • Resources, Risks, Issues • Budget • Completion heatmap • Scope / Buffer • Detailed burnup
  15. 15. • MoSCoW Scope Management • Definition of Priorities • Perhaps better to change names • Now/not now • Discuss what both success, and failure, is
  16. 16. Starting the Kupe Project Note: Contains dummy data to illustrate points.
  17. 17. Completion Heatmap Note: Contains dummy data to illustrate points.
  18. 18. Cost Heatmap Note: Contains dummy data to illustrate points.
  19. 19. Lessons Learned • Scrum does not equal Agile • Early information is double edged • Establish governance structure early, and get buy in • Recognise your short comings, use experts • Confidence in process
  20. 20. Questions?

×