A Thorough Explanation of The Basic Process of Scrum Development!

◆Product Roadmap

A “product roadmap” is a planning tool that shows the vision and strategic direction of a product. In Scrum development, a roadmap has the following roles and characteristics:

1. Deliver the vision : A roadmap shows your team and stakeholders where the product is going and why it’s important.

2. Goals by Time Period : Roadmaps typically list the major features and goals of a product over time. This helps teams understand future priorities and direction of investment.

3. Flexibility : Based on Agile and Scrum philosophies, roadmaps are not fixed. The roadmap should be updated accordingly based on market needs and feedback.

4. Stakeholder Alignment: A roadmap serves as a communication tool with internal teams as well as external stakeholders and management.

5. Relationship with Product Backlog : In Scrum, the “Product Backlog” is a list of specific tasks and requirements. The roadmap provides the strategic direction behind this backlog, providing background and context for which requirements are important and why.

Overall, a product roadmap provides a vision for the future of the system you are investing in. Ideally, plans should be made at the responsible level and implemented after receiving management approval. It’s an important tool that guides your entire team or organization to move in the same direction.

◆Product Backlog

What is a Product Backlog? It is a central artifact in Scrum development that is a prioritized list of features and requirements needed to develop a product.

1. Content: Backlog items are written in the form of user stories, functional requirements, technical tasks, etc., and each item includes information such as value, priority, and effort estimate.

2. Dynamic Nature: Backlogs are not static, and items are often added, removed, or reprioritized depending on market needs or new requirements.

3. Relevance:

・Relationship with Product Roadmap:  A roadmap is a tool that shows the strategic direction and vision of a product. A product backlog, on the other hand, breaks down that vision into specific items and tasks. While a roadmap shows the “what” and “why,” a backlog shows the “how.”

– Relation to Sprint Planning:  During the sprint planning meeting, select items from the backlog to be worked on in the next sprint. The selected items are moved to the sprint backlog and are targeted to be completed by the team during that sprint.

4. Ownership and Management: The backlog is owned and managed by the Product Owner. He defines item priorities through dialogue with stakeholders and conducts refinement sessions with the team to clarify item details and estimates.

The Product Backlog has become a central tool for Scrum Teams to understand the direction of the product and clarify what to do next.

◆Sprint Planning

What is Sprint Planning?

Sprint planning in Scrum development is an important process in which a team decides what to accomplish in the next sprint and plans actions to achieve it. This planning meeting is usually held on the first day of the sprint and involves the Scrum Master, Product Owner, and everyone on the development team.

Sprint Planning Steps:

1. Clarify the purpose: The product owner proposes the purpose and goal of the sprint. This shows the specific results to be achieved and what should be accomplished at the end of the sprint.

2. Select Backlog Items: The Product Owner suggests the highest priority items from the Product Backlog. The development team determines whether it has the ability to implement the proposed item and selects the appropriate amount of the item.

3. Decompose tasks: Decompose the selected backlog items into concrete tasks. This may include tasks such as technical details, design, testing, and documentation.

4. Task estimation: The team makes time estimates for each task. This helps determine whether it is possible to complete the selected tasks during the sprint.

Relationship With Previous and Subsequent Processes:

· Previous Process – Product Backlog Refinement: This is the process of clarifying the details of backlog items and adding/removing new items. During the sprint planning meeting, select items from this refined backlog.

· Post-Process – Sprint Execution: Based on the sprint plan, the team executes the tasks during the sprint. Check progress in daily stand-up meetings and make adjustments as necessary.

Sprint planning is an important phase that begins the Scrum development cycle. Through this plan, the team defines the next sprint’s deliverables and determines specific actions to achieve them. We work closely with pre- and post-processes to maximize the value of the product.

◆Sprint Backlog

What is a Sprint Backlog?

One of the core elements of Scrum development, the sprint backlog is a list of specific tasks that a team aims to accomplish during a particular sprint, managed and managed during the execution (actual development) phase of the sprint. It will be an important tool to use.

Features of The Sprint Backlog:

1. Selected Items : Items from the Product Backlog that are selected during the Sprint Planning Meeting are brought into the Sprint Backlog.

2. Task Decomposition : The sprint backlog breaks down the specific tasks to complete each backlog item. This often includes tasks such as coding, testing, and documentation creation.

3. Transparency : The sprint backlog is accessible to the entire team and provides an at-a-glance view of the progress and completion of tasks during the sprint.

4. Dynamic Nature : If new information or awareness arises during the sprint, the sprint backlog may be updated accordingly. However, since it has already moved to the execution phase where many developers are involved, it is important to avoid changing the purpose or scope of the sprint, and to prevent such changes from occurring, discussion and consideration should be made in the previous stages. should be completed.

Relationship Between Sprint Backlog and other Artifacts:

· Product Backlog : The Sprint Backlog is created based on selected items from the Product Backlog. These items are required to achieve the sprint objectives.

· Increments : At the end of a sprint, when all the tasks in the sprint backlog are completed, a new product increment is expected to be produced.

The sprint backlog is a key artifact that helps the team clarify what it will accomplish in the next sprint and how it will accomplish it. This tool provides a central reference point for monitoring the progress of tasks during the sprint and making adjustments as needed.

◆Daily Scrum

What is Daily Scrum?

The Daily Scrum is a short stand-up meeting that takes place every day during Scrum development. The purpose of this meeting is to help the team communicate, share the day’s progress and challenges, and plan the next 24 hours.

Features of Daily Scrum:

1. Time Constraints : Meetings typically aim to last no longer than 15 minutes, giving you time to focus on the day’s work.

2. Standing : It is common for participants to conduct meetings while standing, which is expected to keep the meeting short and energetic.

3. Three Questions : Each participant will be required to answer the following three questions.

· What did I accomplish yesterday?

· What am I going to accomplish today?

· What are the obstacles or challenges in my work?

4. Location and Time : It is recommended that the Daily Scrum occur at the same time and location each day. This makes it easier to incorporate it into your team’s daily routine as a routine.

5. Facilitation : The Scrum Master acts as a facilitator for this meeting, ensuring that it runs effectively and in line with objectives and time constraints.

6. Importance of Daily Scrum :

· Visualize Progress : Teams can share progress on their daily work to clarify where they are relative to their goals.

· Early Detection of Obstacles : By sharing the challenges and obstacles faced by team members, support and cooperation can be provided to resolve them early.

·Coordination and Cooperation : Encourage team coordination and collaboration to achieve effective work and speed problem resolution.

The Daily Scrum is one of the core practices in Scrum development and is an important tool for facilitating team collaboration, sharing progress, and resolving daily challenges and obstacles. This short meeting brings the team together and helps them work together to effectively deliver the value of your product.

◆Sprint Review

A sprint review (also simply referred to as a “review”) is an event that takes place at the end of each sprint, and is a time for the development team to demonstrate the results of the sprint to stakeholders and other team members.

Purpose of Sprint Review :

1. Collect feedback : Receive feedback from the product owner and stakeholders (users) and use it to inform planning for the next sprint.

2. Validate the Value Achieved: Demonstrate the features and functionality that were actually created and confirm that they are delivering the expected value.

Main activities of sprint review :

1. Demonstration : The development team demonstrates in action the backlog items achieved during the sprint.

2. Collect Feedback: Product owners and stakeholders provide feedback based on the demo and make adjustments to the product backlog as needed.

3. Consider Next Steps : There may be early discussions about plans for future releases or efforts for the next sprint.

important point :

· Sprint reviews are a forum for communication with stakeholders, not a formal approval process.

· Unfinished or half-completed features are not suitable for demonstration.

· A review should be an interactive session, not just a presentation. Ideally, there will be an active exchange of questions and feedback from stakeholders.

Sprint review is one of the most important events in Scrum development. This allows teams to regularly publish their work and receive feedback, giving them the information to make appropriate adjustments to the direction of the product.

◆Retrospective

A retrospective (often abbreviated as “retro”) is when a team looks back at the most recent sprint, discusses what went well during the sprint, what could be improved, and plans for the next sprint. This is an event to clarify what needs to be improved and what needs to be continued.

Main Purpose of Retrospective :

1. Self-Evaluation and Growth : Teams evaluate their own processes and behaviors and decide on specific actions for growth.

2. Continuous Improvement : Through retrospectives, Scrum Teams develop a culture of continuous improvement and find ways to improve efficiency and productivity.

Main Steps of Retrospective :

1. Opening : A short ice-breaking activity or introduction to help participants relax and establish an atmosphere of open communication.

2. Data Collection : Share information and data about events and situations during the sprint to align participants’ perceptions. For example, this may include a review of timeline activities or specific metrics.

3. Gain Insights : The team discusses data and information to identify key issues and successes during the sprint.

4. Deciding on Actions : The team decides on specific actions and improvements to be taken in the next sprint in response to the issues and issues that emerged during the discussion.

5. Closing : Before concluding the meeting, participants share their feedback and impressions of this retrospective and discuss improvements for next time.

Important Point:

· Retrospectives are not the place to criticize individuals. The aim is to provide support for collaborative learning and improvement.

· Effective retrospectives require an environment that fosters open and honest communication. It is important to ensure a safe environment.

· The determined action must be concrete and actionable. You also need a mechanism to track whether the action will be performed in the next sprint.

Retrospectives are an important practice for Scrum Teams to learn from past experiences and plan future actions. This event is designed to support continuous improvement and growth of teams and is one of the core values ​​of Scrum.