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.

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

Clean-up and replace Teamwork chapter #383

Open
2 of 3 tasks
Tracked by #374
egpbos opened this issue Dec 3, 2024 · 2 comments
Open
2 of 3 tasks
Tracked by #374

Clean-up and replace Teamwork chapter #383

egpbos opened this issue Dec 3, 2024 · 2 comments
Labels
Milestone

Comments

@egpbos
Copy link
Member

egpbos commented Dec 3, 2024

  • Add a section to Best Practices.
  • Remove the chapter PR
  • Afterwards: check for broken links (globally! the PR link checker only checks changed files...)
@egpbos egpbos added this to the v1.0 milestone Dec 3, 2024
@egpbos egpbos added the dash label Dec 3, 2024
@egpbos egpbos self-assigned this Dec 4, 2024
@egpbos
Copy link
Member Author

egpbos commented Dec 4, 2024

I'm wondering a bit what we should add on this. In the PR we mention our teams protocol, which indeed we could link to (like we link to the PMP elsewhere), but is this really a software engineering best practice? That protocol in particular feels more like a management solution to me. You cannot really "do or don't" having a team, you either have it (and then there's best practices for working with them I guess) or you don't.

Actually, we do have a nice overview paper on all of the ways this can work, which is on Zenodo somewhere I'm sure (@c-martinez have the link?), maybe that one is good to refer to?

@egpbos egpbos removed their assignment Dec 4, 2024
@c-martinez
Copy link
Member

Not in Zenodo, but here is the doi: 10.1109/MCSE.2022.3167448

@egpbos egpbos moved this to In review in Guide sprint Dec 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: In review
Development

No branches or pull requests

2 participants