Lab Team Meeting: Planning

In your Cell Society teams, take some time to prioritize, organize, clarify, and assign the project's features that will be done this Sprint.

Resources (Reminder)

This series of short blog posts describes how to think about managing your project using Gitlab (along with GIT):

• Always start with an issue
• It's all connected in Gitlab
• The Gitlab Issue Board
• Code Review via Gitlab Merge Requests

The quick summary is:

• create Issues before you do the work
• move and tag those issues on Gitlab's Issue Board
• close or update issues with your commits or Merge Requests
• use Merge Requests to resolve concerns and stay on track

Plan Collaboratively

Discuss your goals and dependencies to create a reasonable timeline to get things done:

• determine the team's priorities for what needs to get done first
• determine what things those priorities depend on
• collect Issues into categories that reflect when they could get done and how they are related
• assign specific Issues to each team member
  NOTE, if the same or similar Issues need to be done by multiple people on the team, create one Issue per person for that task

The result of this planning should be Issues in Gitlab created, assigned, and categorized with tags.

Start Coding the Project

By tracking your Issues in detail your team (and other stake holders) will see the following benefits:

• gives your team a better understanding of the work involved
• helps each team member know what to work on and when
• makes it easier to complete all the work
• provides more accurate status of how the project is progressing

This is only effective if you update your progress regularly by changing an Issue's status online through Gitlab's Issue Board or using keywords in your GIT commit messages.

Submitting your Work

Update your project's Gitlab Issues.