How to Stop Managing and Start Meeting Deadlines
On December 1st, 1913 Henry Ford installed the first moving assembly line. It was brilliant. His innovation reduced the time it took to build a car from more than 12 hours to two hours and 30 minutes. Ford increased production and decreased costs. His brilliant plan moved the automobile from one station to the next until it was complete. Today, the world is a lot faster. Unfortunately, most teams and projects still follow this 100-year-old model to a T (get it… Model T).
Rugby Teamwork & Management
In 1986 two rugby fans Hirotaka Takeuchi and Ikujiro Nonaka created a new approach to projects and teamwork. In this new approach the team “tries to go the distance as a unit, passing the ball back and forth”. Today, we call this agile project management framework Scrum.
Scrum is the leading agile development methodology, used by Fortune 500 companies around the world. It’s a framework or a way of thinking about projects that allow you to be organized and dynamic while not wasting time on project management. There’s no better place to learn about SCRUM then the SCRUM Alliance.
The Scrum framework in 30 seconds
- A product owner creates a prioritized wish list called a product backlog.
- During sprint planning, the team pulls a small chunk from the top of that wish list, a sprint backlog, and decides how to implement those pieces.
- The team has a certain amount of time — a sprint (usually two to four weeks) — to complete its work, but it meets each day to assess its progress (daily Scrum).
- Along the way, the ScrumMaster keeps the team focused on its goal.
- At the end of the sprint, the work should be potentially shippable: ready to hand to a customer, put on a store shelf, or show to a stakeholder.
- The sprint ends with a sprint review and retrospective.
- As the next sprint begins, the team chooses another chunk of the product backlog and begins working again.
Scrum vs Traditional Waterfall Project Management
Scrums work a bit differently than your traditional project management, most organizations will use both due to the different needs of projects.
I recommend Scrums when a project’s needs change and there are a lot of moving parts that can happen simultaneously. The Scrum framework allows different people to pick up tasks and work them independently. You can hit roadblocks while continuing in another area of the project. This flow is agile and can feel chaotic without the proper tools.
The traditional waterfall is great when a project must naturally move in a static linear fashion. For example, at TierPoint I need a private cloud with multiple servers built. First, the networking team must create the private network. Then the virtualization team can create the VMs. Then the Windows team installs the OS. Each team has to wait for the team before them completes there tasks. While we could still use a Scrum framework, the more traditional tools of waterfall project management are helpful.
In Rugby, you barely have any equipment. Likewise, agile projects want a small dynamic tool-set that won’t get in the way. Meet Microsoft Planner.
Planner comes directly with your Office 365 and it’s fantastic.
Planner is Microsoft Office 365’s task management app for teams. The app’s design is based on the Scrum framework. At the top level, you have plans. Each team or project can have its own plan. Within a plan you have buckets. A bucket is a way to organize tasks. A task is a piece of work that must be completed. Tasks can move around the different buckets, be assigned to different people, have comments, etc. It will make more sense as we move through it.
How to get Started with a Simple Plan
Next, we’re going through a simple way to use the Scrum framework and Planner. The most basic plan is a team to-do list. Open the Planner app and create a plan. It will automatically have a to-do bucket. From there you can add members and create tasks.
Team members will know what tasks are available to work because the task won’t have an assignee. When a team member starts working a task, they should mark the task ‘in progress’ and assign the task.
When the work is completed, they can mark the task completed and move on to the next task.
How to add Team Meetings
So you’ve created your plan and added your members. Everyone’s working tasks and things are going well. Things are moving quickly, and the team is growing, we’ll need to start to discuss tasks in a daily or weekly meeting. During the meeting, you can open the ‘Show Completed’ section and talk about completed tasks.
Now we need tasks to go through quality testing before being closed. Create a new bucket called ‘QA’. When a team member completes a task that needs a second person to review, they’ll move the task to the QA bucket. Someone from QA can pick up the task and perform there testing prior to closing the ticket. If QA fails, they can add a comment and move the task back to the To do bucket.
Tier 2 Support Required!
Now our team has grown. We have new interns that can handle most things but every once in a while they need assistance. Now that we have two tiers we create another bucket called Tier 2. When an intern cannot complete a task they can add their notes to the task then move it over to the Tier 2 bucket. Voila!
Waiting on Parts
Now, we need to add hardware to the project. After the parts are ordered a task can be created to keep the team updated on the order status. We don’t want to clog up the To do bucket with tasks that cannot be worked. We’ll need to create a new bucket called ‘On Hold’. Then the task can be placed in the On Hold bucket. Once the parts arrive and the task can be worked we’ll add a comment to the task and move the task to the proper bucket.
Planner is built right into Office 365. If you’re subscribed to Office 365 you can get started right away. The Planner app is lightweight and dynamic. You can make it fit your team and goals, not the other way around.