¿Qué es SCRUM? - Aprende SCRUM en 10 Minutos | Metodologías Ágiles

Introduction to Scrum

Overview of Development Methodologies

• Gabriel introduces the topic of Scrum and its significance in software development, promising a comprehensive overview within 10 minutes.

• He explains that development methodologies are ways to organize work in software development, highlighting two main types: Waterfall (traditional) and Agile (rapid application development).

Waterfall Methodology

• Waterfall is described as a linear approach where each phase must be completed before the next begins, creating dependencies between stages.

• The initial phase involves gathering all client requirements before any coding starts; this is crucial for project success.

• Following requirements gathering, the design phase occurs where solutions are conceptualized and specifications created for implementation.

Implementation and Verification

• The implementation phase is when developers write code based on gathered requirements and designed specifications.

• Verification or testing allows clients to review the product against initial requirements; it’s essential that the system is fully complete at this stage.

Challenges with Waterfall

• A significant drawback of Waterfall is its slow pace; by the time products are delivered, client needs may have changed due to lengthy phases.

• This rigidity can lead to inefficiencies as every phase must be entirely finished before moving forward.

Introduction to Agile Methodology

Transitioning from Waterfall to Agile

• Agile methodology focuses on iterative development, allowing teams to deliver functional components quickly rather than waiting until all features are developed.

Key Features of Scrum Framework

• Scrum facilitates adaptation in response to changing user requirements through short delivery cycles, enabling teams to adjust priorities continuously.

Core Elements of Scrum

Sprints in Scrum

• The concept of "Sprint" is central; it represents a fixed period (1–4 weeks, typically 2 weeks standard), during which specific work commitments are made by the team.

Artifacts in Scrum

• There are three fundamental artifacts:

• Product Backlog: A comprehensive list of tasks needed for project completion including new features and bug fixes. Maintained by the Product Owner who prioritizes items.

• Sprint Backlog: Items selected by the development team for implementation during a Sprint after a planning meeting.

Sprint Goals and Commitments

Implementation of Scrum

Key Concepts of Scrum Implementation

• The implementation of Scrum is crucial as it allows for measurable outcomes at the end of each sprint, which serves as a metric for project progress.

• Scrum consists of sequential events or meetings during each sprint aimed at aligning the team towards a common goal and ensuring workflow efficiency without bottlenecks.

• Backlog grooming is typically the responsibility of the Product Owner, who prioritizes tasks to ensure effective project completion; however, some teams may involve all members in this process.

Sprint Planning and Execution

• During sprint planning, the entire workload for the upcoming sprint is determined by the team based on defined sprint goals, with user stories moving from product backlog to sprint backlog.

• Each team member must validate selected user stories to ensure that the scope of work is realistic and achievable within the sprint timeframe.

Review and Retrospective Meetings

• At the end of each sprint, an informal meeting occurs where team members demonstrate their completed work to stakeholders for feedback.

• The retrospective meeting allows teams to discuss what worked well and what didn’t during the sprint, fostering an environment for open dialogue about potential improvements.

Daily Stand-Up Meetings

• Daily stand-up meetings are brief (15 minutes max), where each member answers three questions: what they did yesterday, what they plan to do today, and if there are any blockers.

• Keeping these meetings concise helps maintain focus; standing up encourages urgency and prevents comfort that could lead to prolonged discussions.

Roles in Scrum

• Two essential roles in Scrum are the Product Owner and Scrum Master. The Product Owner focuses on understanding business needs and prioritizing development tasks based on customer value.

• The Scrum Master acts as a facilitator who trains both the team and external stakeholders in Scrum processes while promoting its principles throughout the organization.

Visual Management Tools

• A key component of Scrum is using a board (Scrum Board), which visually tracks ongoing work status. This board should be accessible to both team members and non-team members alike.

• Teams customize columns on their boards according to their workflow needs, moving user stories through different states as progress occurs during sprints.

Understanding User Stories

• User stories define units of work with standardized formats that make them easily understandable by anyone involved in or familiar with a project.

• An example format includes: "As an end-user, I want to register on the site so I can access my profile." All user stories must meet acceptance criteria before being considered complete.

Conclusion