Placing magnetic card on scrumboard

Whether new to Scrum or a seasoned pro,

Scrum||Falcon – scrumboards.com/falcon

Scrum||Hawk  scrumboards.com/hawk and  

Scrum||Eagle – scrumboards.com/eagle

provides great support for a one-three, four-eight and six-ten person Scrum team to do Scrum Development well, iteration after iteration. It makes Scrum easier.

Physical Scrum Task-boards and Scrum development

Many teams like having a physical scrumboard to complement their scrum software subscriptions out there since they improve the Scrum experience by:

  • Broadcasting the project’s status to everyone involved
  • Acting as a central focal point during daily standups
  • Increasing trust and motivation within teams
  • Being more cost-effective than subscription services
Usable as a whiteboard

Usable as a Whiteboard

History

Physical  Task-boards/Scrumboards boards aren’t new to Scrum development. A quick Google search of “physical Scrumboard” brings up endless images of cluttered whiteboards covered in post-its and in the midst of an iteration.   

Scrum originated in early 1986 during a study by Ikujiro Nonaka and Hirotaka Takeuchi which was printed in the Harvard Business Review. By 1993, Jeff Sutherland developed the Scrum process, while Ken Schwaber applied a different approach with his company. Together, they developed this technique further and formalized it in the year 1995 and named it the Ken Schwaber Scrum software development method.

  • https://en.wikipedia.org/wiki/Scrum_(software_development)
  • https://en.wikipedia.org/wiki/Kanban

Since Scrum development’s beginning in the early ‘90’s, it has become one of the most popular methodologies for software since it creates better quality products in less time than traditional method. Scrum-as-a-service subscriptions are now big business and are sold to a multitude of companies. Even though these software models work well for non-collocated teams, many saw the benefits of having a physical Scrumboard inhouse, especially for Scrum adoption.

In the summer of 2011 Scrumboards.com’s founder  saw teams who were having their highly-paid employees spending a lot of time creating scrumboards, sometimes doing so incorrectly. I decided to create tools that would cut costs and foster a better Scrum experience for teams.

Some people have Duct tape on the wall and it looks like crap. I agree its functional/pragmatic and its horses for courses but your having an expensive software team use that tool.
Although it’s a great Scrum-adoption tool for teams, the goal was to give homemade scrumboards a professional look & feel while also saving companies time and money.

Components

Three sizes of specialized  Task-board:

3 x 4 ft , 4 x 6 ft and  4 x 8 ft
  • Specialize white boards with imprinted template of an Inner Task-board, Burndown chart, and Impediments area. Inspired by Scrum and Kanban development methodologies.
  • Magnetic and Dry Erasable – white board is magnetic and has a dry-erase surface.
  • Dual sided – there is a plane whiteboard on the back!!! Which is really good for liberal discussions in development.
  • Mobile – it comes on aluminum frame and castor wheels with ‘breaks’
  • Easy set up of the task-board with no wall mounting necessary.

Specialized Cards:

User Story Green Six inches by four inches Id/Title, Description, Points and Priority on areas on the cards
Defects Red Six inches by four inches Id/Title, Description, Points and Priority
Tasks Blue Six inches by four inches Id/Title, Description, Points and Priority
Sub-tasks Grey Four inches by four inches Id/Title, Description, Owner and Time on areas on the card.

All cards are magnetic; they magnetically mount onto the Task-board and into the Backlog Holder.

All card have a dry-erase surface and thus are reusable.

Another bonus is they each come with a little dry erase pens each. 🙂

Dry-erasable Task Cards

Dry-erasable Task Cards

 

This was an old version of the cards… I tried to go with Five incehs by four incehs and  three by three but it did not work out.

Now the cards are a little larger and easer to work with.

 Blue, Red and Grey Cards

Blue, Red and Grey Cards

Green User Story and Grey Sub Task Cards

Green User Story and Grey Sub Task Cards

SCRUM FALCON

  • Three foot by four foot ScrumBoard
  • 15 Green User Story Cards for an iteration
  • 15 Red Defect
    Cards
  • 10 Blue Task Cards
  • 20 Gray Sub-Task Cards
  • Up to 8 cards in the Stories column
  • Iteration Backlog Holder displays up to 30 cards

SCRUM EAGLE

  • Four foot by eight foot ScrumBoard
  • 35 Green Cards, 30 Red Cards, 20 Blue Cards
  • 40 Gray Cards
  • Up to 22 cards in the Stories column
  • Iteration Backlog Holder displays up to 45 cards
  • Classic magnetic whiteboard on backside
  • Lightweight frame with four wheels

SCRUM HAWK

  • Four foot by six foot ScrumBoard
  • 25 Green Cards, 20 Red Cards, 15 Blue Cards
  • 30 Gray Cards
  • Up to 16 cards in the Stories column
  • Iteration Backlog Holder displays up to 90 cards
  • Classic magnetic whiteboard on backside
  • Lightweight frame with four wheels

Backlog Holder

Cards in Backlog holder

Cards in Backlog holder

Has cascading pockets to hold the specialized cards and and entire Backlog Holder mounts onto board. It constructed from steel and all magnets are secured. It is sand blasted white.
“Its so easy to sort  and resort the cards in business value in the backlog.”

 

 

Visibility and Transparency

Physical Scrum Task-boards makes it easy for a team to see and adapt to the facts of a project. The following is clearly broadcasted:

  1.  What are the team is actively working on
  2. How much of the overall project is completed
  3. How much have the team spent so far
  4. What may get delayed and why

More Success and Less Costly Changes and Failures

Our physical Scrum Task-boards keep goals clearly defined for developers while providing simplicity. They increase success by the following success-oriented principles:

  1. Scoping – Management builds a list of work according to their highest return on investment to be completed between one week and one month increments.
  2. Prioritizing – Management prioritizes the scoped list of work based on business value.
  3. Timeboxing – A fixed time of one week to one month increment is allotted for the scope. If developers are not meeting their targets, time does not increase, scope is reduced.

Short Feedback cycles inherent in Scrum allow incremental delivery, early measurable return on investment, early and continuous customer feedback, and reduces product and process waste.

Physical Scrum Task-boards help reduce the costs of project changes and failing projects because you can detect the need to adapt or failure much earlier. This means less money is wasted when compared to traditional methods.

Scrum||Falcon

 

Improves the Scrum Experience

  • Provides an authentic model of Scrum.
  • Provides all the benefits of Scrum
  • Provides an easy to use, out-of-the-box Scrum experience for those new to Scrum
  • Complements all other Scrum tools

 

Leave a Reply

Your email address will not be published. Required fields are marked *

 
(function($) { })( jQuery );