Jeff Dalton is Broadsword’s President, Certified Lead Appraiser, CMMI Instructor, ScrumMaster and author of “agileCMMI,” Broadsword’s leading methodology for incremental and iterative process improvement. He is Chairman of the CMMI Institute’s Partner Advisory Board and President of the Great Lakes Software Process Improvement Network (GL-SPIN). In 2008, Jeff coined the term “Process Debt” to describe the crushing, over-bearing processes too many companies employ to achieve a CMMI rating. He is a recipient of the prestigious Software Engineering Institute’s SEI Member Award for Outstanding Representative for his work uniting the agile and CMMI communities together through his popular blog “Ask the CMMI Appraiser.” He holds degrees in music and computer science and builds experimental airplanes in his spare time. You can reach Jeff at firstname.lastname@example.org.
QUEST 2014 Conference and EXPO Sessions:
Throughout the world, IT and Software Engineering organizations are embracing agile methods to take advantage of the benefits of incremental and iterative delivery. Large corporations and the Federal government are increasingly directing software developers to “be agile,” but business practices related to marketing, procurement, project management, and systems definition are anything but. These business organizations all heavily outweigh software development both in budget and in influence. And so, while more developers are living in an agile world, the business continues to live in waterfall surroundings. It’s not a conflict that is easily resolved, but there is opportunity to take control of the debate.
Agile resiliency is about strengthening and reinforcing agile values, methods, and techniques so that it can scale and thrive in this conflicted environment. This is done by integrating with the architectural strengths of the Capability Maturity Model Integration (CMMI), a proven and widely adopted framework used to deploy a continuous improvement infrastructure. While the CMMI has been successfully deployed for years in support of more “traditional” engineering projects, it is methodology agnostic allowing its strength to be leveraged to strengthen agile methods as well. Why not embrace both?
- Hear about a Resilient Agile Architecture to strengthen agile values, methods, and techniques so that they will scale, thrive, and survive
- Discover how to apply the CMMI to make agile methods more resilient as large-scale adopters move to exert influence over standards and methods
- Learn nine new ways to interpret the most important CMMI practices from the perspective of agile teams