Scrum (quick & simple)

These days, agile methodologies are a much more accepted best practice, when compared with waterfall. Scrum is the most common form of the agile project development methodology. Kanban is also common and is typically used for an operations team, help desk, or other team where the work comes in smaller less predictable pieces. A "scrum" is a rugby term where the team of players all link arms and move together as group, so it's all about being a team. Agile development emphasizes flexibility. As with any methodology, there are notable advantages and specific things to watch out for.

The main advantages of Scrum

The main challenges with Scrum

The User Roles

The main Concepts

Release/Project Planning

Tying together the many sprints that are needed for the entire project to be created.

  1. Identify User Stories for the release: Identify the most critical user stories in the product backlog for a given release
  2. Prioritize + Estimate time for the User Stories: Prioritize and estimate work for the user stories in the backlog for the given release. If a user story takes too many days of development, break it down into smaller elements with more manageable chunks (so we can see hours of development per item rather than days of development per item).
  3. Effort estimates: Estimates should be done by hours, days, and months, where estimates are rounded up the the next higher bucket. Often Fibonacci series are used up till about 20d or so. Buckets may be, for example, 1h, 2h, 4h, 8h, 1d, 2d, 3d, 5d, 10d, 1m, 2m, 3m. But any item that's more than a few days should be broken out into smaller tickets that get esimated, and the estimates of the higher item should be the lower items accumulated (ideally using a Gantt chart).
  4. Take the time to add the details: Put in the time and effort to build out all of the needed tickets. The people doing the work need to be the people doing the time estimating. This way there is actual accountability and buy in.
  5. Plan out sprints in the Release: Sprints should be kept as short as possible while being realistic. The goal is to do several sprints (each with their corresponding sprint backlog) can be done in parallel for a given release.

Day-to-day Sprint Progress

At the end of each Sprint


Contact Julian

Get in touch and chat about your company or project.

Julian Cash     415.738.9385     julian@HireThisGeek.com or see the contact page.

BusOps Systems
BusOps Philosophy
Project Management
System Admin
Image Fun