Skip to content

Instantly share code, notes, and snippets.

@JimCampagno
Created June 6, 2018 18:11
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save JimCampagno/65b616c544c893173b640b80aefbe1bd to your computer and use it in GitHub Desktop.
Save JimCampagno/65b616c544c893173b640b80aefbe1bd to your computer and use it in GitHub Desktop.

Sprint Planning

General Notes

  • DON'T think of Pivotal Tracker as a hinderance to the creative hive-mind of the company.
  • DO think of it as one of the members of the team. This mindset will allow us to properly integrate it into our flow.

After our sprint planning meeting is over, we are off to the races:

We each have our own lane as a team. But I want us to get into the mind-set of treating the active sprint as an active race. The path is set, it is on us to go down it to complete the tasks.

The lane should be considered impenetrable during an active sprint. Just as you wouldn't shout out different instructions to the horse as it was in the middle of racing to the finish line. Any new desired task should wait until we are off to the races again (which would be the next sprint).

If we allow new tasks to be added to an active sprint, it has a ripple effect:

There are clearly circumstances that can arise where this has to go down like the above diagram involving the NEW TASK. But it should be the last resort. We want to create a well defined machine that can churn out great work and that's done by allowing for clear paths for us to do what we do best, create.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment