[WIP] NEW CHAPTER - Project Management Frameworks #3416
Conversation
✅ Deploy Preview for the-turing-way ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
| 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] |
There was a problem hiding this comment.
Just double-checking if this reference is already in the references or needs to be added?
There was a problem hiding this comment.
Batool, looks like it might need to be added
There was a problem hiding this comment.
@Arielle-Bennett I will add it.
There was a problem hiding this comment.
Thank you so much @Arielle-Bennett and @BatoolMM for doing this in my absence!!!
book/website/project-design/project-management-methodologies/overview.md
Show resolved
Hide resolved
book/website/project-design/project-management-methodologies/overview.md
Outdated
Show resolved
Hide resolved
| | **Methodology/Framework** | **Approach** | **Key Features** | **Flexibility** | **Change Management** | **Suitability** | **Origin/typically used in** | **Focus** | **Outcomes** | **Readiness for Use in Research Projects** | **Adaptability for Research Projects** | | ||
| |------------------------|--------------------------------|----------------------------------------------------------|-------------------|--------------------------------|------------------------------------------------------|--------------------------------------------------|--------------------------------------------------|--------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------| | ||
| | **Agile** | Iterative and incremental | Flexibility, adaptability | High | Welcomes changes | Complex projects with variable requirements | 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** | 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 | 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. | |
There was a problem hiding this comment.
Noting that this was flagged for inclusive language (scrum master) but I don't think there's any alternative scrum term...
There was a problem hiding this comment.
Unfortunately that's true, @Arielle-Bennett. The scrum community hasn't taken very well to the idea of changing their language to be more inclusive. I struggle with it myself.
See: https://www.scrum.org/forum/scrum-forum/40445/renaming-master-scrum-master
|
On the table, maybe we can just split it into two parts so it renders better? Or have the methodologies across the top and the qualities down the side? |
I added some of these as review suggestions then realised I should probably just open a PR to commit them instead 😄
Arielle-Bennett
added
the
book-dash-nov23
…verview.md Co-authored-by: Arielle-Bennett <74651964+Arielle-Bennett@users.noreply.github.com>
|
Hey lots of interesting information and thoughts! However, one should work a bit on the accessibility of this chapter, a lot of terms are simply thrown at the reader without explanation nor references. If the prerequisite is "none" then one need to assume the reader does not know what project management means, even less what a project management framework is. He will not know what waterfall PM means for instance and will get frustrated. What helped me a lot is when I was confronted with the four components of PM (managing team, data, resources and risks). If I get it correctly, the PM framework is mostly about managing team (and to a lesser extend resources) ? Also make sure you do not write for software projects only, this book is about reproducible research, which means a broader audience and slightly different type of "project" to manage :). There might be some more material to grab at https://carpentries-incubator.github.io/managing-computational-projects/ |
Thanks @jcolomb for the comments. Yes, you're right about the accessibility. This was a quick and dirty draft, which is intended to link out to many subchapter that will be drafted with content around the terms that are "thrown at the reader" here. I was encouraged in the book dash to provide smaller pull requests rather than a huge one, contributing all at once. I think it might need to be edited and revised in an iterative manner, because of this. Regarding the software projects, that's one of the challenges here, I think. But I agree with you, and I really want to bolster this section with case studies/examples of working both in more research-oriented settings with the different frameworks, and also provide examples from my own work with helping research software being developed. Thank you also for sharing the carpentries link. I hadn't encountered that before so that'll definitely prove to be helpful. |
|
Hey @kallewesterling - we'd love to see you back at Book Dash this summer to finish off this chapter! ❤️ Are you able to join us this time around? Applications are open until 26 April: https://docs.google.com/forms/d/e/1FAIpQLSdd7Zy6YUxPRpTmvd3yrtE9w7JCb9tA20NVQ-PmtGPsaRsqww/viewform 😄 |
Summary
Adds in a new chapter on project management frameworks.
Resolves issue #3386.
List of changes proposed in this PR (pull-request)
What should a reviewer concentrate their feedback on?
Acknowledging contributors