Product Driven Programme Management
What does that mean, to be ‘Product Driven’? The CHAOS report, the largest ever study on the attributes of successful IT Projects concluded that traditional IT Project Management methodologies are overall detrimental to the success of IT solutions, resulting in lower success rates, higher cost overruns, greater schedule overruns and larger scope reductions. Quite simply, traditional project management will likely result in poor project outcomes.
To be ‘Product Driven’ means that we predominantly manage Programmes of work by working at the coal face, engineering requirements, developing processes and testing solutions. We are Senior Technical Product Managers with extensive Project Management Experience. Why?
- Software is entirely unambiguous. To increase velocity (speed of development) through a development cycle, your requirements must be clear, well organised and packaged so that a development team can interpret what is being asked
- You can’t manage a project if you don’t understand the nuance. A traditional Programme Manager will spend time asking questions, we spend our time giving answers
- Well written requirements also provide quality test scripts as a by-product. Quality test scripts are one of the most important artefacts for change management. Product Development, Black Box QA and Change Management are not exclusive roles, they are different tasks to be undertaken at different stages of the project lifecycle, ideally by the same person
We Design
A technical product manager who can translate business objectives into actionable development requirements
We Manage Change
Structured UAT and training sessions built on the foundations of easy to interpret test scripts
We Test
The same product owner can black box test (and automate) functional requirements, ensuring a robust system delivery
We Can Talk to the Board
Just because we're in the detail, doesn't mean we're missing the bigger picture. Understanding the nauance means we can address all stakeholders with confidence
Multi-Disciplined
Your Gantt chart won't save you.
Every project needs a plan, but a successful plan has lots of detail, it’s not simply a task list. Before a plan can be delivered, it needs to be understood.
Requirements Elicitation
Iterative development relies on frequent requirement elicitation at the lowest level of detail
Process Design
Understand the business objective and the use case. How do you define done otherwise
Solution Design
Designing data models, logical workflows, use cases, wireframes and more
Change Management
Small, well defined requirements result in effortless estimation and budget control
Testing
Ensuring a robust system is delivered with automated testing that supports future releases
Implementation
Structured UAT and training sessions built on top of clear requirements and test cases
What clients say about our Managed IT Services
