登录查看更多内容

What are the best IT project governance models for large-scale projects?

由人工智能和领英社区提供技术支持

IT project governance is the process of defining and implementing the roles, responsibilities, policies, standards, and procedures for managing and overseeing IT projects. It is essential for ensuring alignment, accountability, quality, and value of IT projects, especially for large-scale ones that involve multiple stakeholders, complex requirements, and high risks. In this article, you will learn about some of the best IT project governance models for large-scale projects and how to choose the most suitable one for your context.

此文章中的业界达人

由社区从 6 条内容中精选。了解更多

Raghvendra Pratap Singh

ICT Program Director (General Manager -Service Delivery) at Ericsson Global India Pvt Ltd
Ratish R. Shetty

KPMG | Associate Director | IT Advisory | Business Applications | IT Business Partnering | SAFe? Agilist | PRINCE2…
Srinivas Jaggumantri

CTO @ Infosys, financial services| Top voice | agile coach | Driving Digital Transformation with Generative AI |…

1 Traditional model

The traditional model of IT project governance is based on a hierarchical and centralized structure, where a steering committee or a project board is responsible for making key decisions, approving changes, and resolving issues. The project manager reports to the steering committee and follows a predefined plan, scope, budget, and timeline. The project team executes the tasks and deliverables according to the plan and communicates with the project manager regularly. This model is suitable for large-scale projects that have clear and stable objectives, requirements, and stakeholders, and that follow a linear or waterfall methodology.

添加您的观点

Joris Van Rillaer

sustainability and regulatory project manager
举报内容
In my experience this model is used more with organizations with a high focus on IT delivery and less on business flexibility. It's less flexible and dynamic for business but has a few advantages: - during a heavy transformation the clear planning and responsibilities can provide certainty and stable objectives which are very likely to be met. - scope creep will be very limited - the planning is clear to everyone - project requirements are well documented Off course, there's a reason why most large-scale organizations and projects have switched to a different model: - project governance is very heavy - little flexibility in adapting to latest priorities - different priorities between business & IT might jeopordaize the project's success.

已翻译

赞

2 Agile model

The agile model of IT project governance is based on a flexible and collaborative structure, where a product owner or a customer representative is responsible for defining and prioritizing the project vision, goals, and features. The project manager or the scrum master facilitates the agile process, removes impediments, and ensures alignment with the project vision. The project team works in self-organizing and cross-functional units, called scrum teams, that deliver incremental and iterative value to the customer. This model is suitable for large-scale projects that have dynamic and uncertain objectives, requirements, and stakeholders, and that follow an adaptive or agile methodology.

添加您的观点

Manav Phull

Consulting Partner at CGI
举报内容
The most popular framework in North America for implementing Agile and Lean practices on a larger scale is known as SAFe (Scaled Agile Framework). It unifies these two methodologies and is typically used at an organizational level, making it well-suited for larger projects that involve multiple teams and business units. Another one, that I have seen large projects implement is Scrum of Scrums where representatives from each scrum team present progress, highlight challenges and coordination needs

已翻译

赞

3 Hybrid model

The hybrid model of IT project governance is based on a combination of the traditional and agile models, where a steering committee or a project board oversees the overall direction, scope, and budget of the project, while a product owner or a customer representative defines and prioritizes the project features and value. The project manager or the scrum master coordinates the integration and communication between the traditional and agile components of the project. The project team works in a mix of waterfall and scrum teams, depending on the nature and complexity of the tasks and deliverables. This model is suitable for large-scale projects that have both stable and dynamic elements, and that require a balance between control and flexibility.

添加您的观点

Raghvendra Pratap Singh

ICT Program Director (General Manager -Service Delivery) at Ericsson Global India Pvt Ltd
举报内容
Hybrid model is the best fit in any of the IT complex & large projects based on my vast experience. Three level regular governance is required i.e. - module/ scrum level (independent) - project level (independent) - program level (integrated/centralised) - Steering progress review This way Scope creep, dependencies/risks and Schedule can be managed incl customer business priorities

已翻译

赞
Tyrell Perera

Enterprise Solution Architect | Cloud and Distributed Systems | EAI
举报内容
Scaled Agile Framework (SAFe) can be considered a hybrid model for IT project governance. It combines elements of both traditional and agile methodologies to provide a framework for scaling agile practices in large organizations. Overall, SAFe provides a balance between the structured control of traditional methodologies and the flexibility and responsiveness of agile approaches. This makes it a well-suited option for large organizations that need to scale agile practices while maintaining governance and control.

已翻译

赞

4 How to choose

When selecting an IT project governance model for large-scale projects, there is no one-size-fits-all solution. The best model will depend on the project characteristics, organizational culture, stakeholder expectations, and external environment. To choose the most appropriate model, consider the objectives, requirements, and risks of the project. Assess how clear they are among stakeholders and what project management methodology is preferred. Additionally, consider how complex, interdependent, and uncertain the tasks and deliverables are; how much authority and autonomy the team members need; and how frequent, transparent, and effective communication and feedback mechanisms are. Lastly, evaluate how adaptable and innovative the project is to changing customer needs and market conditions. Answering these questions will help you assess each IT project governance model's strengths and weaknesses so that you can select the one that best fits your project context and goals.

添加您的观点

Ratish R. Shetty

KPMG | Associate Director | IT Advisory | Business Applications | IT Business Partnering | SAFe? Agilist | PRINCE2 Agile | DevOps | ITIL | Tech Enablement & Operations | Application Management | TOGAF | People Manager
举报内容
Just because a traditional model (e.g. Waterfall model) has a potential to fail doesn't categorically mean it must not be used. If the requirements, success factors, measurements are very clear at the beginning of the project, waterfall method can prove inexpensive and useful. Selecting a IT project governance model for large scale projects requires a thoughtful analysis of project characteristics, organizational culture and specific requirements. Consider the following - 1. Understand Project Complexity 2. Evaluate Flexibility needs 3. Consider Organizational culture 4. Identify stakeholder's involvement 5. Review past project experiences (if any) 6. Examine regulatory and compliance requirements 7. Evaluate Project Lifecycle

已翻译

赞

5 Here’s what else to consider

This is a space to share examples, stories, or insights that don’t fit into any of the previous sections. What else would you like to add?

添加您的观点

Srinivas Jaggumantri

CTO @ Infosys, financial services| Top voice | agile coach | Driving Digital Transformation with Generative AI | Consulting and advisory to global firms
举报内容
It is a fast-changing world and today, more is spent on migrations and modernisations than on new developments in established firms. The governance model needs to factor in legacy in traditional means and have scaled agile governance for the new. It is good to have 3 to 4 weeks of joint planning to create the governance dashboard with key metrics and value levers. Ensure the governance covers value delivered, team productivity, tech dept accrual and reduction numbers. Last, explore how AI can help in the project governance with deeper instrumentation of ALM and DevOps and Configuration systems and real-time analytics.

已翻译

赞

IT Strategy

+ 关注

给文章评分

我们借助人工智能创建了此文章。您认为这篇文章怎么样？

很棒不太好

举报此文章

查看全部

What are the best IT project governance models for large-scale projects?

1

2

3

4

5

1 Traditional model

2 Agile model

3 Hybrid model

4 How to choose

5 Here’s what else to consider

IT Strategy

给文章评分

感谢您的反馈

更多IT Strategy相关文章

更多相关阅读内容

What are the best IT project governance models for large-scale projects?

1

2

3

4

5

1 Traditional model

2 Agile model

3 Hybrid model

4 How to choose

5 Here’s what else to consider

IT Strategy

给文章评分

感谢您的反馈

查看其他技能