Richard Robinson

About Richard Robinson

Chief Architect,

12 things CIOs must understand before implementing Agile

Introduction As we all know, Agile is big business. It takes up pages in Forbes and the Harvard Business Review, it’s galvanised huge consultancies, it has even spawned what has been called (with varying degrees of enthusiasm) an ‘Agile Industrial Complex’. How much is the global Agile ecosystem [...]

Traditional versus Agile methodology

What’s the difference between traditional methodology and Agile methodology? A meditation on the paradox of Agile methodology and what psychologists term ‘locus of control’. Traditional methodology submits the development process to control by artefacts – procedure, standards, tools, etc. That is, it turns developers from engineers into instruments of the [...]

By |2018-09-14T14:18:16+00:00Friday, September 14 2018|Categories: Agile, All, Empowerment, Methodology & lifecycles, Principles, Process and method, Waterfall|0 Comments

Validating your plans

One crucial element of all planning that is frequently ignored is the fact that the planning process will itself frequently lead to changes. You get new ideas, unexpected implications evolve before your very eyes, new information is discovered, and so on. So before you commit to delivering, validating the plan [...]

By |2018-09-11T14:59:48+00:00Tuesday, September 11 2018|Categories: Agile, All, Methodology & lifecycles, Planning, Process and method, Quality|0 Comments

Basic rules for testing for non-testers

Even where Agile teams include expert users, there are still key vulnerabilities in their coverage of the whole end-to-end development process – especially in testing. In mature Agile teams, developers should have good testing skills too. But given that most teams aren’t mature and the trend to retain separate development [...]

By |2018-09-06T17:45:56+00:00Thursday, September 6 2018|Categories: Agile, All, Process and method, Skills, Testing|0 Comments

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
Want to do more than just build systems?             
error: Agile201 is wholly copyright and copy-protected.