Disclaimer: I'm not a scrum master but I have some decent training and implementation in project management due to my engineering background
What is Scrum?
Scrum is a project management approach usually used in software projects but has also grown popular in different fields. The scrum approach is Iterative and flexible in nature while also being customer-centric, with this approach we segment work and deliverables into manageable portions and give value/deliverables as early as possible. This then cycles on and continuous review and feedback are incorporated within the project period
Unique terms in Scrums:
Sprint: Is the segment duration wherein the work is done, it usually ends with giving the deliverable and then review for another cycle or sprint. 1 sprint can last a week or 6 weeks.
Product Backlogs: A list of the work and requirements needed to be accomplished. Usually this are prioritized from succeeding steps in data like ETL processes and dashboarding activities
User Stories/Epics: The description of the requirement or simply the milestones within the project described as scenarios or use cases. Epics are just encapsulations of user's stories within a certain categorization of work. Examples of these are User stories needing filters for specific purpose and an epic of this is the whole filter set in the whole dashboard
Product Owners: The middleman between the customer or stakeholders to the team doing the Product backlog activities. They translate what is needed to be done to the team then explain and present the progress or deliverable submitted to the stakeholders. Example is a sales director is the customer for a sales dashboard then a sales business analyst it the product owner between them and us the data analyst/professional
Scrum Master: The one that leads the team who is doing the product backlog activities, most likely the one overseeing all the tasks done and do daily standups to ensure work progress and load allocations with each member. Usually you are also the scrum master if the project is not that big.
Scrum Team: The ones doing the activities in the product backlog list and ensure all deliverables are achieved within the sprint
Why is this perfect for Analytics/BI projects?
Most Analytics projects consist of making Dashboards and Reports, which may seem simple work to customers but usually has hidden complexities/roadblocks when the project has been started. Also, there are times when customers sometimes don't know what they want until they see what they have. Plunging you the analyst to endless revisions with no end in sight. By implementing Scrum we can easily manage work and expectations for both sides. Here are specific reasons why:
-Adaptable: Scrum is adaptable due to its iterative flow, with review and priority-setting sessions integrated in-between sprints. Scope creep can be quickly addressed in the early stages and the end goal is more apparent every cycle. Common in Dashboards are revisions in the contents, the computations and aesthetics of the view, so its very compatible with the scrum approach. Nontheless with the vision and mission stated you will still have the definite need for revision
-Early Delivery of Value: Each sprint end will always have a deliverable that can be useful and informative enough for the customers to utilize or consume. Usually you can make sample reports in excel before going to automation, then going to the actual report or dashboard.
-Cross-Functional Collaboration: the scrum promotes a collaborative approach within the team utilizing each member by giving them tasks suited for them all while maintaining communication and visibility within the team
-Transparency: Being collaborative in nature work and direction are laid out from the start and during the process. With this Stakeholders and Product Owners see the work that is being done and the team knows the direction and goal they need to achieve and land on
-Faster Problem Resolution: Being transparent and tracked, problems can easily be identified and addressed. just following the flow. it can then be prioritized to the next segment or sprint
Doing Scrum
So how do we execute scrum? and what activities are done to achieve deliverables efficiently and effectively. Below is a simple phase and cycle of a project life cycle in scrum detailed with activities and usual tools I used for each.
I. Initiate - This is where stakeholder meetings are made to ensure the vision and mission of the project. Identify the involved people in doing and directing the project. Have a general plan for the Product backlog deliverables, list of activities and Project schedule
Tool: Project Charter
II. Project Plan and Estimate - In here meeting is conducted within the team to which activities are given to whom and what activities and deliverable will be done within the current sprint.
Tool: Asana Board or Trello (Basically any tool wherein you can list the activities and designate them.
III. Implement - This where activities are performed and daily stand ups or to do are conducted
Tool: Asana Board or Trello (Basically any tool wherein you can list the activities and designate them.
IV. Review and Retrospect - This where the deliverable for the current sprint is presented wherein the owner and user deem it to pass the requirements or criteria. Usually not met requirements are prioritized to the next sprint and documented.
Tool: Risk Management and Lesson Learned List(documentation of not met requirements)
V. Release - Is the formal turnover of the product. Usually a feedback form is given and completion documents are signed
Tool: 1. Risk Management and Lesson Learned List
2. Feedback form
3. Product Revision History
4. Completion Document
All in all there will still be challenges faced in using the Scrum approach but with a continuous improvement mindset and Customer centric Ideal you can reach the goal as efficient as possible instead of stumbling back and forth with unclear goals, Numerous revisions and slow moving product deliverables
Comments