Collective Data Adopts Scrum
Collective Data Adopts Scrum
With increasing popularity, Agile, a mindset around how we think about doing complex work, is being integrated into the daily routines of workers. The Agile mindset has many frameworks which can be implemented depending on what problems an organization is trying to solve. Currently, Scrum is the most popular methodology being adopted by software companies, including Collective Data.
The Scrum framework fits very well with software development projects. It consists of a simple set of roles, responsibilities, and meetings that never change. The predictable nature of Scrum allows teams to better cope with the unpredictable nature of development projects. Decisions are made from real-world results, rather than speculation. Time is divided into short iterations called “sprints” that require teams to meet regularly, plan next steps, and receive feedback from stakeholders. Scrum supports continuous discovery and learning while keeping the product in a potentially deliverable state.
Team members are all equal in Scrum. Developers don’t just develop and testers don’t just test. The roles in Scrum are: Product Owner, Scrum Master, and Team Member.
Product Owner – The Product Owner is responsible for communicating the vision and prioritizing tasks, but not managing the team.
Scrum Master – The Scrum Master is the facilitator for the Product Owner and Team, removing impediments that may keep the team from achieving goals.
Team Member – The team is self-managing and responsible for organizing the work. They are responsible for achieving the goals for each sprint.
Scrum breaks time into sprints. A sprint can be one to four weeks in duration. The team has the final say as to how much work can be accomplished in a sprint. The Product Owner determines the priority of the work in the team’s backlog and has the final say of what criteria need to be met for the work to be accepted as finished.
The product backlog is a prioritized list of all the work that team needs to complete. It helps the product take shape while the team gets a visual depiction of what needs to be done.
Putting it All Together
Collective Data’s Core development team has defined their Scrum roles and are well versed in sprints operations. They have successfully completed numerous sprints for just over a year and it is now engrained in their daily work habits. The process has created a streamlined workflow where each team member knows the status of the work that must be completed and can fluidly move to the next task once a task is complete. Each sprint ends with a review meeting to ensure that the changes to the product are what the stakeholders need and a retrospective meeting that helps the team improve, grow, and learn.
Completing development projects in a deliberate and careful way and reviewing results after each sprint, helps avoid mistakes. The team assumes responsibility for the end product, since all are equal players in the process. With transparency and a level playing field, team members take ownership of the final product. The positive result for Collective Data is the release of a higher quality product, improved internal time management, a reduction in errors, and fulfilled teams.