In February of 2001, the Agile Manifesto was drafted as statement of the principles that underpin agile software development. In the subsequent 7 years, XP, Scrum, DSDM and other agile methodologies have grown these principles to gain traction across even the largest develompent shops. This guided discussion explores the roots of why this revolution has taken hold. Through example and analogy, participants will increase their understanding of the core differences in assumptions and approaches of agile over traditional methodologies. This understanding is used to explore the mechanics of agile development and the role of the business analysts in making agile software development work.
Learning Objectives:
- The philosphy of agile methodologies match the reality of how software gets built
- The mechanics of agile ensures development follows the philosphy and does not become chaotic
- The business analyst role is to ensure the philosphy and mechanics deliver valueable functionality
Skill Level: Intermediate
|
Jon E. Strickler, JiT Technologies
Jon Strickler has focused on business strategy, process improvement, and applying technology to business throughout his over 20 year career helping local and global clients and partners. He has led management and technology professional services organizations at the big 5, large companies, startup technology companies, boutique firms and as an independent consultant. Experience includes implementing agile, lean and six sigma concepts in manufacturing, service, and software development companies. His experience spans customers in the US, Mexico and Europe. His leadership and management skills were honed in the Corps of Engineers while serving in the US and Korea. Jon holds a Bachelor’s degree in Electrical Engineering from West Point and a MBA emphasizing Engineering Management from the University of Missouri, Rolla.
|
