Introduction toAgile Development

by Tu Hoang

Why do we discuss this topic today?

Because Hai is sida!

Some noted questions

￭ Why do we need to understand Agile?￭ Why is Scrum/Kanban agile?￭ Is Agile hard?￭ How can Agile be applied to

outsourced agencies?￭ How to measure personal

performance with Agile?￭ Many more ...

What will we discuss?

1. Basic Concepts of Agile2. Overview of Scrum and Kanban3. Common Agile Pitfalls

Basic Concepts of AgileThe history, values, Agile Manifesto, principles

1

Waterfall vs. Agile - A quick look

Source: Scaled Agile, Inc.

However ...

Iterative and incremental development are not Agile.

You are agile if ...

￭ value the same things as listed in the Agile Manifesto

￭ no standard template or checklist or procedure to "do agile"

Agile Manifesto

￭ When: Feb 2001

￭ Where: At Snowbird resort in Utah

￭ Who: 17 software developers from XP, SCRUM, DSDM, ASD, Crystal, FDD, Pragmatic, etc.

Agile Manifesto

Agile Manifesto

Source: wearecto2.com

Principles behind the Agile Manifesto

1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.

Principles behind the Agile Manifesto

2. Welcome changing requirements, even in late development.

Principles behind the Agile Manifesto

3. Working software is delivered frequently

Principles behind the Agile Manifesto

4. Business people and developers must work together daily throughout the project.

Principles behind the Agile Manifesto

5. Projects are built around motivated individuals, who should be trusted.

Principles behind the Agile Manifesto

6. Face-to-face conversation is the best form of communication (co-location)

Principles behind the Agile Manifesto

7. Working software is the principal measure of progress

Principles behind the Agile Manifesto

8. Best architectures, requirements, and designs emerge from self-organizing teams

Complex Adaptive System Theory

Common Agile MethodsSCRUM, Kanban

2

SCRUM

More detail in Part 2

Kanban

More detail in Part 2

Common Agile PitfallsIt’s not always working

3

Common Agile Pitfalls

People try to learn Agile to look for some new “practices”, some new “processes” to employ them into their existing systems.

Common Agile Pitfalls

Waterfall of “sprints”

Common Agile Pitfalls

Lack of commitment from business.

Common Agile Pitfalls

Inability of programmers and business people to understand each other.

Common Agile Pitfalls

Lack of overall project design.

Failure to pay attention to design can cause a team to proceed rapidly at first but then to have significant rework required as they attempt to scale up the system.

Common Agile Pitfalls

Allowing technical debt to build up.

Common Agile Pitfalls

Developers use the guise of Agile to avoid planning and to avoid creating documentation required for future maintenance.

Common Agile Pitfalls

Student syndrome

Common Agile Pitfalls

Stand-up meeting as report duty.

Thanks!Any questions? Yes, slide #3

My answers to slide #3 questions are not in these slides.You can find me at http://tuhoang.me

See you in part 2

Credits

Special thanks to all the people who made and released these awesome resources for free:￭ Presentation template by SlidesCarnival￭ Photographs by Unsplash & Death to the Stock

Photo (license)