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 4 - Architecture Precursors

 Architecture Precursors: Precursors to modern Enterprise Architecture (EA) include early frameworks like IBM's Business Systems Planning (BSP), which focused on aligning business strategy with information systems, as well as other Information Systems (IS) architecture methodologies that emerged in the 1970s and 80s, emphasizing the connection between business processes and IT systems, laying the groundwork for the holistic view of an organization that EA represents today; the "Master Plan for Information Systems" by Evans and Hague is also considered a foundational concept in this area. Drivers: internal / external pressure enforce to change the system Aims & Directives: Aims:  Goals Objectives Requirements Directives: Principles (example: Principles can be associated with business, data, applications, infrastructure, or security) Policies (example: Members of the public have minimal access to data) Business Rules (example: A rule directs and restricts a procedure)
Post a Comment
Read more

Scaled Agile Framework (SAFe)

The Scaled Agile Framework (SAFe) is a set of organizational and workflow patterns for implementing agile practices at an enterprise scale. The framework is a body of knowledge that includes structured guidance on roles and responsibilities, how to plan and manage the work, and values to uphold. Scrum is a simple, flexible approach to adopting Agile that's great for small teams. SAFe is an enterprise-wide Agile framework designed to help bring Agile beyond the team and into the company as a whole. Scaled Agile has built a comprehensive level that includes all the four layers called the team, program, large solutions, and portfolio level. 4 Layers: Portfolio - Strategy, Vision, Roadmap, Strategy goal, Decision making, Budget, Portfolio level metrics,  Program - Align multiple teams towards a common mission, Bring together all the Agile teams, transparency, collaboration, and synchronisation, Scrum of Scrums, Product Owners to define the overall vision. Large Solutions - ar...
Post a Comment
Read more

4 T's - Technology, Time, Teamwork, Transparency

 1) Technology: Software development technologies are the tools and methods that developers use to design, develop, test, and deploy software applications. These include a wide range of software technologies, such as programming languages, frameworks and libraries, databases, and cloud computing platforms. 2) Time: A timebox is a fixed time period within which a deliverable must be produced in a project management context. It's a time management technique that involves dividing time into individual time periods, each with its own goal, duration, and deadline. Timeboxes are self-contained calendar events that can't be extended once they've started. The fundamental principle of timeboxing is that time in timeboxes can't shift, and once the time runs out, work must stop, even if the task isn't finished.  3) Teamwork: Teamwork in project management is a measure of how well a project's team works together to achieve a goal. It involves collaboration, communication, a...
Post a Comment
Read more