Agile Fine-Tuning
Published August 17th, 2009 Under Project Management | Leave a Comment
Recent work by James Coplien (the course instructor) with Scrum inventor Jeff Sutherland came to a radical conclusion: that though Scrum sounds very simple on the surface, it is in fact painfully intricate underneath (see http://jeffsutherland.com/scrum/2008/02/scrum-and-organizational-patterns.html). There is a well-understood incremental (agile!) path to making Scrum work. Understanding this path, and understanding your current practices, can help you appreciate how much work you need to do to be Scrum-ready, Scrum-proficient, or to optimize your Scrum organization for hyperproductivity. Attendees will learn how to use Organizational Patterns to diagnose, repair, and improve their Scrum implementations.
Agile Architecture Is Not Fragile Architecture
Published June 12th, 2008 Under General | Leave a Comment
Architecture is perceived as a heavy-weight activity which does not fit into an Agile process, so many teams start without it, just to find themselves re-doing the software later because the code structure was not good enough to support maintainability and evolution. In this presentation, Coplien and Henney describe how to start with enough architecture to ensure long term success of the project.
Coplien is a Senior Agile Coach, and Systems Architect working at Gertrud&Cope. He is a well-known industry speaker, author, and innovator. Henney is an independent consultant and trainer based in Bristol, UK. He has developed and delivered training courses, consultancy and software across a number of domains.
Coplien and Martin Debate TDD, CDD and Professionalism
Published February 29th, 2008 Under Software Testing | Leave a Comment
Debate sprang up at JAOO ‘07 around Bob Martin’s assertion that “nowadays it is irresponsible for a developer to ship a line of code he has not executed in a unit test.” In this InfoQ video, he debated with Jim Coplien on this and other topics, including Design by Contract vs. TDD and how much up-front architecture is needed to keep a system consistent with the business domain model.