Scrum-Mastering

1st Nov 2023: we got a Github badge for repo with many stars! THANK YOU.
Celebrate and share the collective knowledge with others, it's FREE!!!


First of all, THANK YOU for considering contributing to Scrum-Mastery:

THE Open-source project in GitHub for Scrum Masters to chip in add additions to it > to help & learn from each other with the Scrum Framework.

We want to go far, therefore let's go together.

• It’s people like you that make it such a great tool.
• Your contributions help make an Agile journey with Scrum better for everyone, developers and non-developers alike.
• Also is a great way to grow your skills and help others.
• Whatever your skill level, working on open-source is a great way to learn new things.
• Let's build upon each other's ideas as we enable and encourage our teams to do.
• Make a suggestion, fix a bug, improve documentation, or contribute code to a project. Even asking questions helps.
• It's alive! a regenerative collaboration to our work, to "leave the place better than how we found it".

As you have landed here, please make sure you familiarise yourself with:

• The project licence file (Also accounts for any reference, use, view etc of this open-source project)
• CONTRIBUTING & CODE_OF_CONDUCT files

With the motto to keep things simple, we have a base folder structure by each Scrum ceremony in each file containing:

• Antipatters : Things to watch out for that may spoil the broth for your team, do add antidotes too!
• Questions : Powerful yet simple to help reflection, act as an ignator, open possibilities, etc ultimately to serve the team. Good to have in your backpocket.
• Indicators : How do we measure what works? Keeping Systems Thinking at hand so that single metrics don't damage the goodness of the whole. Think of them as leading indicators of a healthy team/product/organisation.

Scrum ceremonies give us rhythm and checkpoints, hence the idea to segregate the content on each of those. //

A little video for visual learners

Check this short intro out: https://youtu.be/B_2zPRtcfZY.

How to contribute to an Open-Project

Please stick with the folder and file structure, adjust the content you want to add in line with those.

A guide to making open source contributions, for first-timers and for veterans. Check this!

You may be new to GitHub, is a simple way to collaborate on content across multiple files and folders, without overriding each other work and building upon each other ideas. See below to get started: Check out this quick tutorial to get you up and running with your first open-source contribution in less than 5 minutes: https://www.youtube.com/embed/dSl_qnWO104

1. Create a GitHub user if you do not have one.
2. Fork the repository (select the account you want to fork it to) - you will have a copy under you now.
3. Clone/Download files so that you can work/edit the files on your machine OR change files directly if you are not familiar with CLI and/or code editor.
4. Once you are ready > commit changes (use comments to briefly describe which changes for maintainer) & Push changes.
5. Create a Pull Request from Master (original repo) and compare the changes.
6. The project maintainer will review changes and communicate for the best contribution it can be!

Text and markdown files are perfect formats, see here how to add formatting

There isn't a better way to learn than to try!

With the recent release on Github web, once you have your own branch you can just type . (yes a full stop) and will open up this repository on web version that you can work from if you prefer or click 'edit' from this page on your branched version, something like this:

You can also ping me here or at https://twitter.com/inescapinezka OR https://www.linkedin.com/in/inesgarciaagile/ for support if need be!

BONUS: Under 5 minutes food for thought on the "Stop Doing Scrum?!", debunking the myth muddle: watch