What's in the Handbook?Schedule of Events
All About Chingu
Your Voyage
Pre-Voyage - Solo Project
Voyage - Team Project
How Does it Work?1. Meet Your Team2. Review Chingu Agile MethodologyOverviewProject ManagementSprints3. Choose Your Project & MVP4. Setup Your Team Workflow5. Develop Your Project6. Project Closure
Pair Programming Guide
Technical Resources
Project Resources

Review Chingu Agile Methodology

Photo by Hitesh Choudhary on Unsplash



Project Management

A Project Manager is not explicitly assigned to Chingu Voyage Project teams. It's up to each team to decide whether they want a teammate to fill this role or if they want to share the responsibility. This functions performed by a Project Manager are important and should not be ignored. To be successful, especially with complex projects, teams need to review the Chingu Agile Methodology and decide how they will follow and monitor it.

You can learn more about Agile Methodology in general in Agile Methodology 101


The Voyage project is divided into six one week long sprints in which you design, develop, and deploy your project. During the life of the project specific sprints have specific goals:

  • Sprint 1 - Ideation: Set up team processes, procedures, select your project, and create the Product Backlog.
  • Sprint 2-5 - Development: Iterate over the items in the Product Backlog to create a potentially deployable product by the end of the sprint.
  • Sprint 6 - Closure: Complete your testing and documentation, deploy your MVP, get feedback from other teams, and prepare to celebrate your success in the Project Showcase!

Sprint 1 - Ideation

Sprint 1 is where your team will select a project and create your initial Product Backlog itemizing the features for it to achieve a Minimum Viable Product (MVP) status by Sprint 6. Which features are needed to reach MVP status are solely decided by your team. However, it's important to manage scope to ensure that you finish by the end of Sprint 6. Remember that it is easier to add new features if you finish early than it is to take out features to meet the deadline.

Keep in mind that maximizing what you learn and achieve in the Voyage Project rests on staying organized, effectively communicating across the team, and ruthlessly managing project scope.

It is suggested that you maintain your Product Backlog as GitHub Issues so you can tag items with labels to associate them with the sprint they are to be created in and to assign them to specific team members. This promotes visibility across the team and makes it quicker to identify when and where there are problems.

Using a GitHub Integrated tool to help manage and track tasks and issues is one way to streamline your development workflow and increase visibility to the project backlog across the your team. We
suggest you consider using ZenHub.

This is also where your team will establish the processes and procedures you'll follow in each of the successive sprints for the duration of your Voyage Project. It's important that these be agreed on by the team, clearly communicated, and understood by everyone on the team.

Sprint 2-5 - Development

These are the sprints in which you'll be creating and testing product features. Each sprint starts with a Review and Retrospective/Sprint Planning Meeting of the prior sprint so improvements can be made to team processes before the new sprint starts. In classic Scrum these are two separate meetings, but we've combined them here to streamline the process and to allow more time to be devoted to development work.

Once the Review and Retrospective part of the meeting has finished the meeting transitions to Sprint Planning for the new sprint that's starting. The output of sprint planning are to identify items in the Product Backlog that are to be completed by the end of this sprint. In GitHub Issues each of these items should be assigned a label for the sprint and assigned to one or more team members.

The remainder of the sprint is devoted to the team completing their assignments, testing, and deploying the potentially deployable product that's the result of the work in this and the preceding sprints. Remember that Scrum is an iterative process.

Sprint 6 - Closure

Your planning should target Sprint 6 for final resolution of any outstanding tasks or issues, deploying your MVP, getting feedback from other Chingu's, preparing for the Project Showcase, and submitting the Post Cohort Survey when it is sent.

Copyright2021 Chingu Cohorts