Skip to content

Latest commit

 

History

History
133 lines (92 loc) · 4.49 KB

README.md

File metadata and controls

133 lines (92 loc) · 4.49 KB
Raw

How to Plan

  1. Brainstorming
  2. Prioritizing
  3. User Story Dependencies
  4. Acceptance Criteria
  5. Defining Tasks
  6. Project Board
  7. Sprinting and Reviewing

Brainstorming

  • What user needs and business problem does this app cover?
  • Who is the user?
  • What is the business?

Prioritizing

How to decide which stories to focus on.

At this stage in planning your team will decide which stories are more aor less important. You will be writing your ideas into a backlog.

Acceptance Criteria

How you'll know when a story is finished.

Now that you have an idea what the project will eventually be like, it's time to get specific. Acceptance criteria are a way to scope and verify your user stories.

Given [context] when [a specific action is performed] then [a set of > > > > >

consequences should occur]

You can write your first-draft acceptance criteria in your backlog, later moving them under each user story in your development-strategy.md, and ultimately creating a checklist in each issue.

User Story Dependencies

How to plan your development schedule.

Some user stories depend on each other, some do not. Figuring out these relationships will make it possible go from a disorganized backlog to an organized development strategy.

Understanding these dependencies can also allow you to develop much more efficiently. You can develope user stories that do not depend on each other in parallel instead of waiting for one to finish before moving on the next.

Here are some questions you can ask yourself to help understand your project:

  • Do I need A in order to be able to build B?
  • Can the user do B without A being available?

A nice way to visualize these relationships is by creating a graph to visually represent dependencies:

Excalidraw is a great tool for collaboratively writing these diagrams.

Defining Tasks

How to break the story into coding tasks.

Answering these questions is a way to break down complex user stories and to determine what code is needed. Following this questions guide will help you fill in the specifications of each step in your development-strategy.md

Handlers are the glue of your user stories. Understanding your answers to these questions will not only help you decide which tasks to develop, but can be used to plan the details of the user story's handler:

  1. User Story Objectives
    1. ... ?
  2. User Flow ?
    1. ... ?
  3. Wireframes ?
    1. ... ?

Project Board

How to manage your team's project

Convert your development strategy into milestones (user stories), issues, labels and a project board. When you create the milestones for your user stories, you can include the acceptance criteria as a checklist in the milestone's description.

This isn't a permanent thing! You can always adjust the project board and development strategy as the project evolves; adding issues, removing issues, adjusting tasks ... whatever is necessary to make the project go smoothly.

Sprinting and Reviewing

The fun part, writing code and closing issues ;)