Even today with Agile software development, it's comfortable to think that prescriptive strategies such as managing changing requirements in the form of a product backlog, holding a daily meeting where everyone answers three questions, having a single requirements owner (and thereby one neck to wring), and other such ideas will get the job done. But we all know that some of these "rules" are meant to be broken.
Advisor
Driven by Process Goals: The Key to Scaling
Posted February 5, 2014 | Technology |
About The Author
Mark Lines is Managing Partner at Scott Ambler + Associates. He is a Disciplined Agile coach, helping organizations all over the world transform from traditional to Agile methods. Mr. Lines also helps customize Agile governance practices to accelerate complex projects in large enterprises. He is coauthor (with Scott Ambler) of An Executive’s Guide to Disciplined Agile and delivers workshops on various Agile topics. He can be reached at mark at… Read More
Scott W. Ambler is a Cutter Expert. He is the cocreator of the Disciplined Agile (DA) framework and thought leader behind the Agile Modeling and Agile Data methods, working with clients around the world to improve the way they develop software. Mr. Ambler is coauthor of several software development books, including An Executive’s Guide to Disciplined Agile, Disciplined Agile Delivery, Agile Modeling, The Elements of UML 2.0 Style, Agile Database… Read More
Don’t have a login?
Make one! It’s free and gives you access to all Cutter research.