Our process starts and ends with the customer, beginning with the idea and ending with a finished product that captures that idea. It’s a combination of Agile, Scrum, and Lean Software Development Processes.
When a customer comes to Red27 Consulting with an idea, more often then not, it’s a vision of what they think might solve a specific problem. Red27 Consulting can help get that idea into actuality by creating User Stories. User stories are stories describing how a feature of the product will work. These will become the basis of work items later in the process and allow for an estimation of the product scope and size.
In order to properly prioritize, we next ask the customer
will order the user stories from highest to lowest priority, creating the backlog of work to do. The order in the backlog can be changed at any time before work has started on any given story. Stories can also be modified, added, and removed as needed as long as the scope, or size, remains in tact.
Once a day the team will meet to determine three thin
gs, what was completed on the previous day, what should be completed today, and any blocking issues that could occur. These meeting are typically very quick, less than 15 minutes. The customer is encouraged to attend these meetings to address any blocking issues that might arise. However, the customer is asked not to modify the user stories during this time. The goal is to keep everyone on track and moving forward.
The development iteration is a one to two week span of time where work is done on the product. The product manager, working with the customer, will keep the next priority items on a Kanban board in the ready column. The team will set a goal at the beginning of the iteration to help focus the development effort.
During the iteration a developer will take one of the items from the ready column and will work on it through completion. An item is completed when it has automated tests and is in the production build of the product. The developer will focus completely during this time and only work on another task if it is a critical issue or the current item is blocked waiting for customer feedback. As much work as possible is done during the iteration. Typically, after two to three iterations a development velocity can be estimated.
At the end of the iteration, the team will review the processes used and implement any needed optimizations. The customer will decide if any of the completed features are not finished and need additional work. If something needs additional w
ork a new story is created and added to the top of the backlog. The customer decides at these meetings if a release should be done.
The end of each iteration contributes to the finished product. Once the user stories have been completed or the customer decides enough as been done to meet their needs, the product is complete.