The next meeting of AgileKC will take place on August 25, 2011 — 6:30 PM
Topic:
Agile and Scrum were forged in a crucible of debate confronting the entrenched waterfall model. To promote the new concepts survival, early champions and advocates composed the “Agile Manifesto,” a succinct proposition articulated as values and principles. Today, organizations see dramatic outcomes without grasping the results are not generated by Agile processes, but by Agile values.
James Peckam gave a presentation at this year’s Kansas City Software Developers Conference which revisited the values on which Agile and Scrum were founded. The presentation discussed how Agile’s core values influence the practices, techniques, pitfalls, patterns and anti-patterns that promote or plague Agile development. The subsequent provocative discussion explored the interplay of conflict, courage, and core values.
James, like many of us, succumbed in 1986 to the siren call of BASIC running on a Commodore 64. By 2003, this had lured him away from a short amateur music career as a bassist and into Information Technology. James started in software/hardware support, progressed into Software Development, and currently works as an Agile Coach/Team Facilitator where some have chosen to call him … ScrumMaster! James has participated on projects that vary from large scale hardware/software implementations to fast-paced start-up “hack-a-thons,” to rapid enterprise-scale web software releases. James is passionate about agile engineering including practices such as Extreme Programming, Behavior Driven Development (BDD), Lean, and Scrum. His certifications include the Certified Scrum Professional and Certified Associate of Project Management. In his spare time he enjoys dining out with his wife (especially BBQ and Thai), or online gaming with First Person Shooters and Massively Multi-player games.
So, reflect on this, the original Agile Manifesto, and we will see you on 08/25/11 at the NEW Pizza Shoppe:
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 tools
* Working software over comprehensive documentation
* Customer collaboration over contract negotiation
* Responding 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.