Why Agile and Scrum Matter

Changes is constant, software development as well. Do you know the development of mobile phones, starting from Motorola DynaTAC (1973) to Iphone 6 (2014). How about the software? The new versions are released with new improvements.

Software is not always able to automatic repairing. Therefore, software should be changed frequently and we need responding to changes.

source: http://answers.microsoft.com/

In working software today, how about customers' collaboration or requirements?

We ignore the fact that many customers don't know what they want.
We ignore the fact that when they know what they want, they can't describe it.
We ignore the fact the even when they can describe it, they often a proposed solution rather than a real need.
We ignore, that a lot of customers give us a solution but not the problem.

source: http://accelerateddevelopment.blogspot.com/

And, in working process, earlier founded bugs are cheaper.

Manifesto for Agile Software Development:

Individual and interaction over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan.

Scrum is an iterative and incremental agile software development methodology for managing product development. Agile is the way to think about responsiveness to changes and Scrum is a framework for increasing the speed and feedback loop.

Waterfall vs Scrum:

Waterfall process

Scrum process

source: https://en.wikipedia.org/

Rather than doing all of one thing at a time, Scrum teams do a little of everything all the time.

Twelve Agile Principles:

1. Produce Value Early	7. Working software
2. Welcome Changes	8. Sustainable development
3. Iterative Delivery	9. Technical excellent
4.  Daily Business Collaboration	10. KISS – Smart, Sexy
5. Trust motivated team	11. Self-Organized team
6. Face to face	12. Reflect, Adjust, Adapt

Things are fit for Scrum:

	Agile	Lean	Kanban	Scrum	XP
Type	The way to THINK	Production PRACTICE	METHOD	FRAMEWORK	Technical PRACTICE
Goal	Responsiveness to changes	Reducing waste	Maximize the flow	Increase the speed and feedback loop	Improve software quality
Implementation	- Agile manifesto - 12 Agile Principles	With principles and practices	Whiteboard	Sprint	- TDD - Paring - Swarming

References:

[1]. "Fit for Scrum" course - Mr. Sebastian Sussmann - CIO, Axon Active Vietnam
[2]. http://www.agilemanifesto.org/
[3]. http://www.agilemanifesto.org/principles.html