Lean-Agile software development is a conceptual framework for undertaking software engineering projects that embraces and promotes evolutionary change throughout the entire life-cycle of the project. In Lean-Agile, work proceeds from the initial concept through development, and on to delivery when the customer can consume the product.

Scrum is one of the more popular Agile frameworks. The Scrum Alliance is a group of analysts that originally developed the Scrum processes and the Agile Manifesto. Originally, it was intended for software development projects but can be applied to other applications.

From a Lean-Agile perspective, the goal of Scrum can be summarized as,

The incremental delivery of value through iterative development according to the capability of the team.

Resources in this topic

Alternatives to Scrum of Scrums (Article)
Business Value, the Forgotten Goal (Blog Entry)
Carry-Over Work (Article)
Contrasting the Daily Scrum with Kanban's Daily Stand-up (Article)
Cross-Functional Teams: Improving Communication Between People who Work Together (Article)
Daily Stand-Ups (Article)
Dynamic Feature Teams: When Static Won't Work (Article)
Going Beyond Scrum, Part 1 (Blog Entry)
Going Beyond Scrum, Part 2 (Blog Entry)
Improve Scrum with Leanban (Article)
Iteration 0 - Conduct (Article)
Iteration 0 - Facilitate (Article)
Iteration Planning Meeting - Facilitate (Article)
Iteration Retrospective - Facilitate (Article)
Lean-Agile Team Checklists (Article)
Leanban in Depth (Article)
Meetings for Lean-Agile (Article)
Metrics (Article)
Overview of Standard Work (Article)
Product Demonstration and Review - Facilitate (Article)
Product Demonstration and Review - Plan (Article)
Resistance is Not to Change (Article)
Scrum (Article)
Scrum as Example (Article)
Scrum of Scrums (Article)
Scrum/APM Case Studies (Article)
Types of Tests for Code (Article)
What Framework / Method / Approach Are We Using? (Article)
What Should Team Process(es) Be: Scrum, Kanban, Leanban? (Article)
Writing Tasks (Article)