Planning Approach - Jacob1225/pufferfish-minecraft-mod GitHub Wiki

Our approach to planning out features and requirements happened through brainstorming meetings at the start of each sprint iteration. At each major planning meeting we would look at our existing set of requirements and pick out the ones which we think are high priority. High priority is decided based on whether the feature is a fundamental feature for the game, a feature that would provide the player with a lot of value, or a bug that needs to be fixed. In addition to this, we brainstorm a few more additional features that we feel our mod could benefit from. Since at every iteration, we get a better visualization of what our product can bring, we are able to add requirements throughout the project as older requirements are completed.

Each brainstorming meeting and requirement is jotted down in a sticky note format on a Google Docs. We prioritize each idea and assign them to a developer. Then, we estimate a completion timeline that we think is reasonable for that feature.

Our notes from each meeting can be found on our Shared Google Drive: https://drive.google.com/drive/folders/1kbDxmRJ1nsjIU_qtCOGhLo1A0emNLYsc?usp=sharing

After Milestone 1, we showed significant improvement in the Requirements area.

• We became more organized during our brainstorming meetings by making detailed notes so that everyone can be completely up-to-date.
• We made sure to assign developers to high priority tasks immediately and continuously follow up with them on the progress.
• We were able to make more accurate estimations of timeline and adjust accordingly if there are any blockers.
• We narrowed our requirements scope to focus on the high priority, high impact tickets

Through these improvements our team became of effective in implementation and as a result, we increased the rate of execution and were able to close tickets at a higher rate with less rework.

After making notes during the sprint planning meeting, we formalize the tasks by added them into Jira and assigning them to the appropriate team members. Here is a screenshot of what the list of all our requirements overview looks like in Jira. We use Jira to manage requirements, assign priority and responsibility, and track progress and GitHub branch.

Issues View:

Link to original image: https://drive.google.com/file/d/1l5plUYjqHe8SMosBcDPxtc-RGzx9kl3_/view?usp=sharing

Progress View:

Link to original image: https://drive.google.com/file/d/16n6v5iojENkC4E9XRSk1DDenZNzPad7m/view?usp=sharing

What an individual issue looks like:

Link to original image: https://drive.google.com/file/d/1ZVitGiJXGZ-2A7APU5ZAyHqyGEZ-2h6u/view?usp=sharing