feat Add artifacts section

SDM.md

@@ -78,30 +78,87 @@
 
 ### 1. Introduction
 
-##### 1.1 Purpose of the Document
+#### 1.1 Purpose of the Document
+
 The purpose of this document is to provide a comprehensive guide on how our software development team will use Scrum as the chosen methodology for product development. It outlines the roles, processes, ceremonies, and practices that the team will follow to ensure effective project delivery.
 
-##### 1.2 Scope
+#### 1.2 Scope
+
 This document focuses on the implementation of Scrum within our software development team. It serves as a reference for team members, stakeholders, and anyone involved in the development process to understand how Scrum will be applied.
 
-##### 1.3 Audience
+#### 1.3 Audience
+
 The primary audience for this document includes team members, Scrum Master, Product Owner, and other stakeholders associated with the software development project. It is assumed that the readers have a basic understanding of Agile principles.
 
-##### 1.4 Document Overview
+#### 1.4 Document Overview
+
 This document will provide a comprehensive overview of Scrum, including its roles, events, and artifacts. It will then delve into the specifics of how our team will establish and apply Scrum practices throughout the software development lifecycle. Additionally, it covers metrics, communication guidelines, and integration with existing processes.
 
 ### 2. Scrum Overview
 
-##### 2.1 What is Scrum?
-Provide a brief overview of Scrum, including its Agile principles, iterative and incremental development, and its emphasis on collaboration, transparency, and adaptation.
+#### 2.1 What is Scrum?
 
-##### 2.2 Scrum Roles
-Explain the three primary Scrum roles: Scrum Master, Product Owner, and Development Team. Outline their responsibilities and how they collaborate.
+Scrum is an Agile software development framework designed to enable teams to deliver high-quality software products iteratively and incrementally. It is based on a set of principles and values that prioritize collaboration, transparency, inspection, and adaptation.
+
+Key characteristics of Scrum include:
+
+- Iterative and Incremental Development: Scrum follows a series of fixed-length iterations called "Sprints," typically lasting two to four weeks. During each Sprint, the team aims to create a potentially shippable product increment by completing a set of prioritized work items.
+
+- Empirical Process Control: Scrum is built on the three pillars of transparency, inspection, and adaptation. The team continuously inspects the product and the process to adapt and improve based on the observations.
+
+- Flexibility and Adaptation: Scrum encourages a flexible and adaptive approach. It acknowledges that requirements and priorities can change during a project, and the team should embrace change to deliver the most valuable product.
+
+- Transparency: Transparency is a fundamental value in Scrum. The process, progress, and challenges are visible to all stakeholders, fostering trust and collaboration.
+
+- Continuous Improvement: Scrum promotes a culture of continuous improvement through regular retrospectives, encouraging the team to inspect and adapt their processes for better outcomes.
+
+Scrum's focus on incremental progress, regular inspection, and adaptation allows teams to respond effectively to changing requirements and deliver valuable software in a collaborative and transparent manner.
+
+#### 2.2 Scrum Roles and Responsibilities
+
+##### 2.2.1 Scrum Master
+
+The Scrum Master is responsible for ensuring that the Scrum framework is understood and followed by the team. They act as facilitators, coaches, and servant leaders, removing impediments and fostering an environment where the team can thrive. The Scrum Master also helps in organizing Scrum events and collaborates with the Product Owner and the Development Team.
+
+##### 2.2.2 Product Owner
+
+The Product Owner represents stakeholders and is accountable for maximizing the value of the product. They are responsible for managing the Product Backlog, ensuring that it is transparent, prioritized, and contains items with clear descriptions. The Product Owner collaborates with the Development Team and stakeholders to define product vision and ensure the team delivers the most valuable features.
+
+##### 2.2.3 Development Team
+
+The Development Team consists of professionals who do the work of delivering a potentially releasable Increment of the product at the end of each Sprint. They are self-organizing and cross-functional, meaning they collectively possess all the skills necessary to deliver the product. The Development Team collaborates with the Product Owner to clarify requirements and with the Scrum Master to continually improve their processes.
 
 ##### 2.3 Scrum Artifacts
-Describe the essential Scrum artifacts, such as the Product Backlog, Sprint Backlog, and Product Increment. Explain their purpose and importance in the development process.
+
+Scrum utilizes three essential artifacts to facilitate a clear understanding of the product being developed and the progress made during the development process:
+
+1. Product Backlog:
+
+- Purpose: The Product Backlog is a dynamic and prioritized list of all the work items (user stories, features, bug fixes, improvements) needed to be completed for the product. It represents the requirements and the vision of the product.
+- Importance: The Product Backlog acts as the single source of truth for the development team and stakeholders, ensuring a shared understanding of the product's scope and priorities. It enables transparency and allows for the continuous inspection and adaptation of the project's requirements.
+
+1. Sprint Backlog:
+
+- Purpose: The Sprint Backlog is a subset of the Product Backlog that includes the work items selected by the Development Team to complete during a Sprint. It represents the tasks the team commits to accomplishing during the Sprint.
+- Importance: The Sprint Backlog serves as a plan for the Sprint and guides the Development Team on the work they need to accomplish. It helps the team stay focused and organized throughout the Sprint, as they can visualize the tasks they must complete to deliver the committed Increment.
+
+1. Product Increment:
+
+- Purpose: The Product Increment is the sum of all the completed and potentially releasable Product Backlog items at the end of a Sprint. It is the tangible output of the team's work during the Sprint.
+- Importance: The Product Increment demonstrates progress and value delivered by the team to stakeholders. At the end of each Sprint, the Product Increment should be in a potentially shippable state, meaning that the product is functional and could be released to end-users, even if the decision to release it or not is up to the Product Owner.
+
+Explanation of their Importance in the Development Process:
+
+1. The Product Backlog's importance lies in its role as a living document that represents the evolving requirements and priorities of the project. By maintaining the Product Backlog and ensuring it is transparent, the Scrum Team can make informed decisions during Sprint Planning, Sprint Reviews, and Sprint Retrospectives. This artifact enables continuous alignment with stakeholders and helps the team focus on delivering the highest value features.
+
+1. The Sprint Backlog is crucial because it helps the Development Team understand what needs to be done during the Sprint. By selecting a set of items from the Product Backlog, the team commits to achieving specific goals within the Sprint. The Sprint Backlog serves as a guide during the Daily Stand-up, where team members can track progress and identify any obstacles or challenges that need to be addressed.
+
+1. The Product Increment's significance lies in providing a tangible outcome at the end of each Sprint. It allows stakeholders to see and experience the value delivered by the team continuously. A well-defined Increment, meeting the Definition of Done, demonstrates the team's ability to deliver a functional and potentially releasable product at regular intervals, even if the decision to release it or not is made by the Product Owner. This fosters trust, transparency, and collaboration between the team and stakeholders.
+
+Overall, these artifacts promote transparency, collaboration, and continuous improvement throughout the software development process. By providing a clear vision of the project, measurable goals for each Sprint, and tangible outcomes, the Scrum artifacts enable effective decision-making, alignment, and value delivery.
 
 ##### 2.4 Scrum Events
+
 Outline the key Scrum events, including Sprint Planning, Daily Stand-up, Sprint Review, and Sprint Retrospective. Explain their objectives and how they contribute to the team's success.
 
 ### 3. Scrum Team Establishment