As a technology and management consulting firm, Transforming Solutions implements a variety of project management tools when consulting with clients on a variety of topics: business process improvement, software evaluation and selection, technology assessments, among many others. In fact, not having a project management framework in place could be a reason why projects fail.
TSI prides itself on adapting and pivoting to meet client needs by implementing Scrum project management, when appropriate. Scrum project management is an agile approach often used with software evaluation and selection projects that incorporates interactive practices and small wins to reach the end goal. It uses a set of resources, meetings, and roles that help teams manage and plan their work.
In this blog, we will describe the following Scrum project components:
- The Scrum framework
- Key Scrum roles in a project team
- Scrum deliverables/artifacts to use during a project to stay on target
The Scrum Framework
Going back to school is to a growth mindset as the scrum framework is to an agile mindset. The scrum framework is based on continuous improvement and incremental growth, and it allows a project team to change directions and change where needed. Scrum is structured in small sprints to help project teams adjust to changes flexibly and re-prioritize tasks as needed. These sprints are typically between 2 weeks and 1 month long, but these timelines are flexible and your team can change sprints at any time.
Each Scrum sprint will have 4 main components:
- Sprint Planning Meeting: This meeting should take place at the start of each project sprint and should outline what activities should be completed and milestones should be met within the current sprint. This meeting allows the team to discuss high and low priorities and discuss tasks to be completed during the sprint. It is also an opportunity to look at the project holistically and begin working backwards to accomplish tasks.
- Daily Scrum Meetings: Many teams find value in hosting brief (15 minutes or less) daily meetings to discuss yesterday’s progress, today’s goals, and identify any risks or disruptions that may cause today’s goals from being accomplished. This is an opportunity to get the team energized for the tasks ahead!
- Sprint Review: This meeting is set to demonstrate what has been accomplished during the sprint and get feedback from key stakeholders regarding what needs to change going forward, review milestones that weren’t met, and determine how to achieve those milestones.
- Sprint Retrospective/Reflective: At the end of each sprint, the project team meets to reflect on tasks and activities, and determine opportunities for improvement in the upcoming sprint. This is an opportunity to update any project management documents and finalize any deliverables from this sprint.
Key Scrum Roles
Below are some of the key roles within a Scrum project team:
Product Owner/Product Manager Role in Scrum)- A product owner is the individual on the project team who defines the features, scope and schedule of the project. This individual is responsible for overseeing and achieving the financial goals of the project, and they also prioritize the product backlog and adjust the priority of backlog tasks as needed. The Product Owner’s job is to make the project vision a reality.
ScrumMaster- The ScrumMaster is the individual responsible for enacting and enforcing scrum practices. They coach the project team using Scrum values at the forefront of their methodology which helps improve team productivity. They are what some call a “servant-leader for the Scrum Team” (Scrum Guide). The ScrumMaster does not oversee the day-to-day activities of the project, but provides strategies to move the team forward. They help remove distractions, detailers, and disruptions from the project.
The Scrum Project Development Team- Scrum project teams are typically 5-9 cross-functional individuals, ensuring that the team has the necessary skill sets to accomplish tasks. Titles of team members do not matter, only the work being performed by each team member, and accountability belongs to the entire team, not just one person. This encourages a strong sense of teamwork and ownership among the whole team. As they say in High School Musical, “we’re all in this together!”
Scrum Deliverables/Artifacts
Product Backlog- A Product backlog is a list of all desired work and tasks for a project. It serves as the single source of truth for all project activities and includes a list of details, estimates, and priority values. A priority value is assigned by the Product Owner at the beginning of a project, but this value is subject to change at the beginning of each sprint as tasks are added or priorities shift.
https://www.scrum-institute.org/The_Scrum_Product_Backlog.php
Sprint Backlog- A Sprint Backlog is a micro-set of a Product Backlog. It is a set of items selected for a particular sprint and includes all of the work needed to meet the sprint goals. Members of the project team sign up for their own tasks to complete, and estimated remaining work is updated daily in this document. The Sprint Backlog is a collaborative, iterative document that is constantly being changed and updated by the project team.
Burndown Charts– These charts show a visual presentation of work that still needs to be completed in a sprint, compared to the timeline and plan of work.
TSI implements iterative deliverables (pre-final recommendations and deliverables) whereby we collaborate with the project team by presenting recommendations in phases that are shaped via input by key stakeholders. Phil Jackson once said, “The strength of the team is each individual member. The strength of each member is the team.”
How to get started
Scrum can seem overwhelming. There are constantly moving parts, changes that need to be implemented swiftly, and roles that need to be determined. There is always more work to be completed. However, the goal of Scrum is to accomplish the work in a smarter, more iterative way.
Are there any current or upcoming projects that would benefit from implementing the Scrum framework? Not sure how to get started? Transforming Solutions is ready to help. Email us at tsi@transforming.com to learn more about our project management services.