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

Certified Enterprise Architect Professional (CEAP) - Module 5 - Architecture Frameworks

Architecture Frameworks: An Architecture Framework is a theoretical structure that has the purpose of developing, executing, and maintaining an Enterprise Architecture. Advantages of EA framework: Simplify Breaks down areas of the business process Organise business components and create and identify relationships between business Determine the scope Customization in the existing framework Disadvantages of EA framework: Need to follow process Provides only direction and not information It's based on goal and objective Need creativity and proactive thinking Zachman Framework: The Zachman Framework is a widely used model in Enterprise Architecture (EA) that provides a structured way to classify and organize an organization's information infrastructure by defining different perspectives from various stakeholders, allowing for a holistic view of the enterprise and facilitating alignment between business needs and technology solutions; essentially acting as a template to organize arc...
Post a Comment
Read more

Daily Agile Scrum stand-up meeting guidelines

Followers of the Scrum method of project management will typically start their day with a " stand-up meeting ". In short, this is a quick daily meeting (30 minutes or less) where the participants share the answers to the three questions with each other: • What did I accomplish yesterday?  • What will I do today?  • What obstacles are impeding my progress?  Some people are talkative and tend to wander off into Story Telling .  Some people want to engage in Problem Solving immediately after hearing a problem. Meetings that take too long tend to have low energy and participants not directly related to a long discussion will tend to be distracted. These are the minimum number of questions that satisfy the goals of daily stand-ups. Other topics of discussion (e.g., design discussions, gossip, etc.) should be deferred until after the meeting.  Here are few tips for running a smooth daily meeting:  • Everyone should literally stand-up and no one should sit down ...
Post a Comment
Read more

Empiricism (Scrum)

Empiricism asserts that knowledge comes from experience and making decisions based on what is observed. Pillars of  Empiricism . Various practices exist to forecast progress, like burn-downs, burn-ups, or cumulative flows. While proven useful, these do not replace the importance of empiricism . In complex environments, what will happen is unknown. Only what has already happened may be used for forward-looking decision making. Each artifact contains a commitment to ensure it provides information that enhances transparency and focus against which progress can be measured: ● For the Product Backlog it is the Product Goal. ● For the Sprint Backlog it is the Sprint Goal. ● For the Increment it is the Definition of Done. These commitments exist to reinforce empiricism . The sum of the Increments is presented at the Sprint Review thus supporting empiricism .
Post a Comment
Read more