Richard Robinson

About Richard Robinson

Chief Architect, Agile201.com.

Face-to-Face: Good or bad?

The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. Agile Manifesto - Principle 6 Traditional (especially waterfall) delivery methods are generally very document-heavy. Long before a line of code is written, an ocean of ink is spilt in the form of [...]

By |2018-07-30T12:09:21+00:00Monday, July 30 2018|Categories: All|0 Comments

Big Up-Front Assumptions

“Pro tip: Never assume shared understanding” - Charles Lambdin. Absolutely. In fact, if you’re in a position where a topic is under serious debate (consultancy, coaching, training, change programme, etc.) you should prioritise grasping exactly where your understandings differ, & removing that. From then on, change will be a lot [...]

Managing change fatigue

A key issue with Agile’s high-frequency delivery regime is change fatigue: however promising in principle, there’s a limit to how much change anyone can absorb. But how do you know you’re nearing that limit? Here are Agile201’s Top 10 signals of impending fatigue: Areas being changed resist the latest changes. [...]

By |2018-06-27T20:21:43+00:00Wednesday, June 27 2018|Categories: Agile, All, Change, Implementation|0 Comments

On the truth – or otherwise – of models

All too often I hear people repeating a very old adage about modelling: "All models are wrong, but some are useful." My immediate reaction to this tends to be 'so what?' No, models don't describe the world in detail or provide insight into every facet of it, yet they do [...]

By |2018-06-20T20:36:39+00:00Wednesday, June 20 2018|Categories: All, Methodology & lifecycles, Process and method, Quality, Skills, Stories, Tools|0 Comments

Value: Or why Product Management is fundamental to Agile

When explaining Agile, it's common to describe it in terms of the basic development-and-delivery process from which Agile (and especially Scrum) began: A single development team. Focused on a single iteration (with occasional references to a multi-iteration release). Limited to software development (with an implied but not described software deployment [...]

By |2018-06-20T19:53:39+00:00Friday, June 15 2018|Categories: All|0 Comments
Want to do more than just build systems?             
error: Agile201 is wholly copyright and copy-protected.