Agile & Scrum
Agile & Scrum
Agile Software Development & Scrum Framework
1. Overview of Agile and Scrum: A Software Development Paradigm Flexible to Change
flowchart LR
A["Rigid, plan-centered development"] -- "Shift to iterative feedback and value focus" --> B["Agile & Scrum"]
Definition:
- Agile: An umbrella term for iterative software development methodologies that value people and communication and responsiveness to change over rigid plans and documentation.
- Scrum: The leading Agile framework for tackling complex projects by developing in small units called Sprints.
Characteristics: (Fast feedback) Short sprint cycles (2–4 weeks) quickly incorporate customer feedback to adjust direction. (Continuous delivery) Delivers working software every sprint, continuously generating business value. (Built-in quality) Sprint reviews and retrospectives repeatedly improve both process and quality.
2. Scrum Framework Process and Key Roles
a. The Scrum Development Process (Sprint Cycle)
flowchart LR
A["Traditional development<br/>(fixed requirements)"] -->|"Challenge<br/>(poor responsiveness to change)"| B{"Transformation mechanism"}
B -->|"Iterative development"| C["Scrum Sprint\n(2-4 week cycle)"]
B -->|"Visible feedback"| D["Daily Scrum/Review\n(continuous improvement)"]
C --> E["Delivering customer value\n(Agility & Quality)"]
D --> E
| Category | Key Activities | Purpose |
|---|---|---|
| Sprint Planning | Set sprint goals and select the backlog | Define the work to be done within the sprint |
| Daily Scrum | Share what was done yesterday, today’s plan, and blockers | Synchronize the team and resolve issues immediately |
| Sprint Review | Demo the increment and collect feedback | Stakeholder review and confirmation of business value |
| Retrospective | Identify improvements to process and collaboration | Continuously strengthen team capability and optimize process |
b. The 3 Core Scrum Roles
flowchart TD
ROOT["The 3 Core Scrum Roles"]
PO["Product Owner"]
SM["Scrum Master"]
DT["Development Team"]
ROOT --> PO
ROOT --> SM
ROOT --> DT
PO --> P1["Maximize business value"]
PO --> P2["Prioritize the backlog"]
SM --> S1["Guide the Scrum process and remove impediments"]
SM --> S2["Practice servant leadership"]
DT --> D1["Self-organizing"]
DT --> D2["Develop the increment and own its quality"]
style ROOT fill:#1E3A5F,color:#fff
| Role | Responsibility & Authority | Notes |
|---|---|---|
| Product Owner | Decides “what” to build, manages the product backlog | Accountable for ROI and business outcomes |
| Scrum Master | Guides “how” to collaborate well, protects the Scrum process | Acts as a facilitator |
| Development Team | Technical implementation and quality assurance, cross-functional | A group of 5–9 specialists is recommended |
3. Expected Benefits and Success Considerations of Adopting Agile
| Category | Expected Benefits | Application and Practical Use |
|---|---|---|
| Improved quality | Short-cycle testing and review | Detect defects early alongside continuous integration (CI) and test automation |
| Customer satisfaction | Flexible accommodation of changing requirements | Respond instantly to market needs and improve customer experience through frequent releases |
| Increased productivity | Self-directed teamwork | Remove bottlenecks and create focus through visibility tools (e.g., Kanban boards) |