Skip to main content

AgilePgM Philosophy and Principles

AgilePgM Philosophy:

The agile programme management philosophy is that an agile programme delivers what is required when it is required.

No more no less.

AgilePgM Principles:

1, Programme goals are clearly and continuously aligned to business strategy

A programme will have an overall vision based on the business strategy at the time of definition – all decisions taken within the programme must be viewed in light of this vision.

The vision should be reviewed and validate throughout:

                                                         I.            Upon change to business strategy

                                                       II.            Every time a capability is enabled – has enough been achieved

                                                     III.            At the conclusion of every project within the programme

In order to achieve this, the programme team must:

                                                         I.            Understand the business strategy and priorities

                                                       II.            Establish a valid business case

                                                     III.            Ensure alignment of all constituent projects to the programmes business case

                                                    IV.            Ensure continuous business sponsorship and commitment

                                                      V.            Build in review points

2. Benefits are realised incrementally and as early as possible

Agile programmes will focus on incremental enablement of capabilities which will result in the realisation of benefits. Business can benefit from early benefits. Agile teams can use the lessons learned and adapt

Underlying this principle is:

                                                         I.            Benefits must be prioritised early on – programmes can be designed early on to deliver benefits into the organisation ASAP

                                                       II.            The capabilities that deliver benefits must be prioritised

                                                     III.            Only those capabilities to be enabled in the short term can be planned in detail

Benefits need to be evaluated on a cost/benefit scale

3. Governance focuses on creating a coherent capability

Important to realise Agile projects must be able to incorporate change driven by the programme. Agile projects must align to the programme ultimate vision – to deliver agreed capabilities. Projects and initiatives must be synchronised to ensure they can deliver a capability – coherent across the organisation.

Programme management team must:

                                                         I.            Agree high level project requirements – for each project

                                                       II.            Empower the teams to deliver those high level requirements

                                                     III.            Ensure overlaps between projects are understood and controlled

                                                    IV.            Ensure consistency and synergy across projects

                                                      V.            Constant review of projects to ensure they remain aligned to the programme vision

4. Decision-making powers are delegated to the lowest possible level

It’s important to have the decisions made by the right people at the right time for velocity reasons.

Governance needs to be defined early in the programme and clearly communicated

5. Agile programmes are iterative and have the ability to contain both agile and non-agile projects

Some programmes can engage with non Agile based projects. It’s important that programme teams understand how the different types of projects can be executed successfully within the programme.

Key point – programmes are enabling benefits iteratively and incrementally by means of a series of projects


Comments

Post a Comment

Popular posts from this blog

New way of product development

Today is the era of fast-paced world and competitive world. Companies are realizing that the old sequential approach to developing new products won’t get the job done and product can’t be reached to market when compared to competitors. The 4 stages of product development are as follows – R&D, Growth, Maturation, and Decline. Instead of sequential approach, companies are using holistic approach – as in rugby game, the ball gets passed within the team as it moves as a unit up the field. This holistic approach has six characteristics: 1)     Build-in-instability 2)   Self-organizing project teams 3)   Overlapping development phases 4)   Multi-learning 5)   Subtle (very clear and strong) control 6)   Organizational change to explore and learning The above six characteristics forming a fast and flexible process for new product development with advantage of act as a change agent, creative, market driven ideas, flexi...
Post a Comment
Read more

Product Manager vs Product Owner

Both the product manager and the product owner work towards a common goal, to build and improve products that create meaningful value for customers and all stakeholders within the company. This usually happens by delivering and optimizing product features. Product Manager Product Owner The product manager discovers what users need, prioritizes what to build next, and rallies the team around a product roadmap. The product owner is responsible for maximizing the value of the product by creating and managing the product backlog. This person creates user stories for the development team and communicates the voice of the customer in the Scrum process.      Product Manager and Product Owner's work on below vacuum. Product manager focus on: Business Strategy Long term Product Vision Long term Product Strategy Product Roadmap Alignment with Product Owner Product owner focus on: Release Plan (Product Backlog ie: ...
Post a Comment
Read more

Delivering a project within budget

 Here are some tips for delivering a project within budget: Set a realistic budget Define the project's scope and necessary resources, and create a budget that's realistic. Cost estimate Segment the project into smaller tasks and milestones to plan how to use resources and provide clarity. Divide the project plan Break down the project into tasks to avoid late deliverables and over-budget projects. Monitor progress Regularly track the project's progress to identify and prevent cost overruns. Use progress reports to compare actual costs to the budget. Anticipate and revise changes Communicate with stakeholders to identify and assess risks, and assign owners to each risk. Consider different scenarios Estimation can be difficult for complex projects with many potential outcomes. Tracking: Tracking time spent on tasks, Tracking expenses per project, and Using project management software. Use Historical Data Your project is likely not the first to try and accomplish a specific o...
Post a Comment
Read more