Agile Agile Agile Agile Kanban Lean Continuous-Integration Behavior-Driven CI BDD Test-driven Backlog Scrum Retrospective Estimation Empowerment On-Time Iterative Sprint Paradigm accelerating adoption agile agile-development agile-planning behaviors challenges ci complex-projects continuous-delivery continuous-integration continous-delivery delivery development disciplined distributed first global governance improvement innovation integration iteration servant-leadership lean measured metrics planning practices process-scaling scrum skills software steering stories team teams user-story whole-teams co-location empowerment beyond next sprint-planning kanban work-in-progress lean

1

From wikipedia- Agile ManifestoIn February 2001, 17 software developers[6] met at the Snowbird, Utah, resort, to discuss lightweight development methods. They published the Manifesto for Agile Software Development[1] to define the approach now known as agile software development. Some of the manifesto's authors formed the Agile Alliance, a nonprofit organization that promotes software development according to the manifesto's principles.The Agile Manifesto reads, in its entirety, as follows:We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:Individuals and interactions over processes and toolsWorking software over comprehensive documentationCustomer collaboration over contract negotiationResponding to change over following a plan

That is, while there is value in the items on the right, we value the items on the left more.[1]

2

If you can think up an awkward social situation, there is a Seinfeld episode for that.

In this one, George has hit rock bottom. He has no money, he has no job and he lives with his parents. He is encouraged by his friends to try to do the opposite of what his instinct tells him to do. With remarkable results…

To act contradictory to your instinct, to defy conventional wisdom is what I refer to as the Costanza Effect. Here is looking at Agile and point out where we have had remarkable success by applying the Costanza effect.

https://www.youtube.com/v/RerJWv5vwxc&rel=0&showsearch=0&modestbranding=1&autoplay=0&iv_load_policy=3&version=3&enablejsapi=1

3

4

https://www.youtube.com/v/vWCGs27_xPI&rel=0&showsearch=0&modestbranding=1&autoplay=0&iv_load_policy=3&version=3&enablejsapi=1

5

Henry Ford was no perfect man, but nobody can deny his success. He has validated, retroactively, many of the contradictory positions that Agile has assumed.

6

7

8

Note from the audience:“Confirm: Stand-ups are NOT debriefings done standing up, nor are they interrogations…”

http://www.techrepublic.com/blog/it-consultant/the-softer-side-of-agile-leading-collaborative-teams-to-success/http://www.techrepublic.com/blog/it-consultant/the-softer-side-of-agile-leading-collaborative-teams-to-success/http://www.ambysoft.com/essays/agileRoles.html

9

Big Requirements Up Front (BRUF)Sounds like my dog, a rescue mix of boxer and shepherd.

10

11

From the audience:“how to maintain product consistency with emergent design and architecture?”

Another Note from the audience:“Big Design Up Front (BRUF) hides the iteration and refactoring that occurs during Analysis and Design.

In iterative development the refactoring becomes visible.”

Sprint 0 (if you have to)http://www.pmscrum.com/blog/2011/06/10-things-do-sprint-0Design will emerge…http://www.mountaingoatsoftware.com/blog/agile-design-intentional-yet-emergentArchitecture will emerge…http://www.scaledagileframework.com/the-principles-of-agile-architecture/

12

13

I like this a lot. Quality comes from character, not from a cloak or layer of paint.

14

From the audience:“From pairing comes less code = simpler code”

http://www.scrumalliance.org/system/resource_files/0000/0459/AgileQA.pdf

15