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

Agile Product Management | FLEX from Product Management to the Team (Article)
Alternatives to Scrum of Scrums (Article)
Business Value, the Forgotten Goal (Blog Entry)
Carry-Over Work (Article)
Common Challenges and Their Remedies Faced by Teams New to Scrum and Related FAQs (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)
Flowing Within a Time-box (Article)
Focus on Finishing Stories in the Sprint and on Finishing MBIs in the Program Increment (Article)
Going Beyond Scrum, Part 1 (Blog Entry)
Going Beyond Scrum, Part 2 (Blog Entry)
How Lean-Thinking Helps Scrum (Article)
How to Adopt Scrum Effectively (Article)
Improve Scrum with Leanban (Article)
Iteration 0 - Conduct (Article)
Iteration 0 - Facilitate (Article)
Iteration Planning Meeting - Facilitate (Article)
Iteration Retrospective - Facilitate (Article)
Lean-Agile Product Management (Article)
Lean-Agile Team Checklists (Article)
Leanban in Depth (Article)
Meetings for Lean-Agile (Article)
Metrics (Article)
My Beliefs about Scrum, by Al Shalloway, CEO of Net Objectives (Article)
Net Objectives' Approach To Scrum (Article)
Overview of Standard Work (Article)
Product Demonstration and Review - Facilitate (Article)
Product Demonstration and Review - Plan (Article)
Resistance is Not to Change (Article)
Running Effective Planning Events (Article)
Scrum (Article)
Scrum as Example (Article)
Scrum of Scrums (Article)
Scrum-But: Management interrupts us all of the time with needed new functionality (Article)
Scrum/ATDD Case Studies (Article)
Teaching Scrum as a Supporting Framework Instead of as Forcing Framework (Article)
The Learning Philosophy of Team Agility and Scrum With ATDD (Article)
The Net Objectives Scrum Support System (Article)
The Reasons For Our Approach to Scrum (Article)
Types of Tests for Code (Article)
We do Scrum-but: We don’t estimate because it takes too long or management beats us up. (Article)
What Framework / Method / Approach Are We Using? (Article)
What Should Team Process(es) Be: Scrum, Kanban, Leanban? (Article)
What You Need to Get Started with Scrum (Article)
Why You Should Grow Your Own Scrum Masters Instead of Bringing In Outside Scrum Masters (Article)
Writing Tasks (Article)