Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[WIP] NEW CHAPTER - Project Management Frameworks #3416

Open
wants to merge 5 commits into
base: main
Choose a base branch
from
Open

[WIP] NEW CHAPTER - Project Management Frameworks #3416

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
740408a
Adding in overview
Nov 15, 2023
c423f90
Adding to TOC
Nov 15, 2023
4361878
Update overview.md (#3418)
Arielle-Bennett Nov 16, 2023
8bd7c1a
Update book/website/project-design/project-management-methodologies/o…
kallewesterling Nov 20, 2023
56d75d7
Merge branch 'main' into adding-project-management-methodologies
kallewesterling Jan 30, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 2 additions & 0 deletions book/website/_toc.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -282,6 +282,8 @@ parts:
file: project-design/pd-overview/pd-overview-sharing
- title: Project Design Checklist
file: project-design/pd-checklist
- title: Project Management Methodologies/Frameworks Overview
file: project-design/project-management-methodologies/overview
- title: Creating Project Repositories
file: project-design/project-repo
sections:
Expand Down
53 changes: 53 additions & 0 deletions book/website/project-design/project-management-methodologies/overview.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,53 @@
(pd-frameworks-overview)=
# Project Management Methodologies/Frameworks Overview
(pd-frameworks-overview-prerequisites)=
## Prerequisites
| Prerequisite | Importance | Skill Level | Notes |
| -------------|----------|------|----|
| None |

## Summary
Project management methodologies or frameworks are structured approaches to planning, delegating, tracking, managing changes, and evaluating work across different industries, including research.
They provide clear guidance and direction on how work should be managed effectively, and can support greater collaboration, transparent decision making, and deliberative working.

Arielle-Bennett marked this conversation as resolved.
Show resolved Hide resolved
Choosing the right project management framework for a research project is crucial, as it can significantly influence your research project's success, efficiency, and potential for collaboration.
Research projects are often characterised by uncertainty, evolving objectives, and a need for flexibility.
As such, they require a framework that can accommodate these dynamics.
As a recent study pointed out, "a fine balance is needed between implementing management approaches to support the efficient and effective delivery of projects while not compromising accountability, creativity and innovation." [santos2022framework]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just double-checking if this reference is already in the references or needs to be added?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Batool, looks like it might need to be added

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Arielle-Bennett I will add it.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you so much @Arielle-Bennett and @BatoolMM for doing this in my absence!!!


Traditional methodologies, for example Waterfall, offer a structured, linear approach beneficial for projects with well-defined stages and stable requirements, known from the beginning of the project design process.

Agile frameworks, including Scrum and Kanban, are flexible and can adapt to changing research landscapes and iterative discovery processes that are part of many research projects.

There are also a number of other methodologies and philosophies that can matter to you: PRINCE2, Lean, Stage/Phase Gate, and many more.

The decision between project management frameworks hinges on the nature of the research, the level of clarity in objectives, and the extent to which the project can accommodate changes in scope or direction.
Some methodologies are better suited for flexible collaboration between distributed teams.
Balancing these factors with team dynamics and stakeholder expectations will guide researchers in selecting a framework that aligns with their project's goals, timeline, and complexity, ensuring a smooth and effective research process.

These pages on The Turing Way are designed to assist you in choosing the right project management framework for you.

## Quick comparison between methodologies/frameworks

| **Methodology/Framework** | **Approach** | **Key Features** | **Flexibility** | **Change Management** | **Suitability** |
|-------------------|-------------------|--------------------------|-------------------|----------------------|-----------------------------------|
| **Agile** | Iterative and incremental | Flexibility, adaptability | High | Welcomes changes | Complex projects with variable requirements |
| **Scrum** | Iterative, time-boxed sprints | Roles (Scrum Master, Product Owner), Artifacts, "Ceremonies" | Moderate to High | Adapts to changes in sprints | Projects that benefit from regular reassessment |

Check warning on line 35 in book/website/project-design/project-management-methodologies/overview.md

View check run for this annotation

In Solidarity / Inclusive Language

Match Found 


Please consider an alternative to `Master`. 
Possibilities include: `primary`, `main`, `leader`, `active`, `writer`
Raw output 
/master/gi
| **Kanban** | Continuous flow | Visual workflow (Kanban board), WIP Limits | High | Adapts easily to changes | Work with varying priorities and volume |
| **Waterfall** | Linear and sequential | Sequential stages, Documentation-heavy | Low | Resistant to changes | Projects with well-defined requirements |
| **PRINCE2** | Process-driven, structured | Defined roles, Stage controls, Tailorable | Moderate | Controlled changes | Large, complex projects requiring tight control |
| **Stage/Gate (Phase Gate)** | Structured, phase-based | Defined stages, Gates for review/decision | Moderate to Low | Controlled at each stage | Projects that need regular reviews and checks |
| **Agile Stage Gate** | Blend of Agile and Stage Gate | Combination of flexibility and structured decision points | High | Welcomes changes amidst stages, controlled gates | Complex projects requiring regular reassessment |

-----


| **Methodology/Framework** | **Origin/typically used in** | **Focus** | **Outcomes** | **Readiness for Use in Research Projects** | **Adaptability for Research Projects** |
|------------------------|--------------------------------------------------|--------------------------------------------------|--------------------------------------------------|--------------------------------|----------------------------------------|
| **Agile** | Software development, creative projects | Customer satisfaction, team collaboration | Incremental improvements, adaptability to change | Highly suitable due to its iterative nature, allowing for frequent reassessment and adaptation as research findings evolve. | Extremely adaptable, can easily integrate new research directions and findings. |
| **Scrum** | Software development, product development | Team productivity, Iterative development | Deliverables at the end of each sprint | Suitable for research projects that can be broken down into smaller, iterative cycles, with regular reassessment points. | Adaptable within each sprint cycle, but less so between sprints. |
| **Kanban** | Operations management, maintenance projects | Workflow efficiency, Limiting work in progress | Continuous delivery, Improved flow efficiency | Suitable for ongoing research projects with continuous tasks and shifting priorities. | Highly adaptable to changing priorities and can handle evolving research needs seamlessly. |
| **Waterfall** | Construction, manufacturing | Comprehensive planning, Documented process | Predictable results, Detailed documentation | Less suitable for research due to its rigid structure and difficulty in accommodating changes once the process has begun. | Low adaptability, not ideal for research projects where requirements and goals may evolve. |
| **PRINCE2** | Government, large corporate projects | Project governance, Control mechanisms | Project completion within specified constraints | Moderately suitable, especially for large-scale research projects needing stringent control and structured management. | Moderate adaptability, with some flexibility within its structured framework. |
| **Stage/Gate (Phase Gate)** | Product development, large-scale engineering projects | Stage completion, Risk management | Go/No-go decisions at each phase, Risk mitigation | Moderately suitable for research projects that are large and complex, requiring systematic review at each phase. | Moderate adaptability; changes are generally feasible at specific stages, but less so mid-phase. |
| **Agile Stage Gate** | R&D, product development | Agility with structured reviews | Agile flexibility with stage-wise decision making | Highly suitable for research, combining the flexibility of Agile with the structured review process of Stage Gate. | Very adaptable, offering the benefits of Agile’s responsiveness with added decision points for reassessment. |