Home » Agile (page 5)

Agile

The illusion of agility (what most Agile transformations end up delivering)

Agility is a unique and continuously evolving state that is typical to a specific organization with its people and its history. A traditional (industrial) approach to becoming more Agile commonly creates no more than an illusion of agility. Agility is a specific state as it reflects the uniquelessons and learnings that an organization and its inhabitants went and go through, the way in which ...

Read More »

“Agile Coaching” Is Not the Goal

I’ve met a number of agile coaches recently. They tell me they’re hired as Scrum coaches or as Scrum Masters. They see their job as “better Scrum.” It would be lovely if that was their one and only job. However, many of these coaches work in organizations just starting a cultural transformation. Even though the client asked for agile coaching, ...

Read More »

The power of small declines

Last year I wrote about the power of 1% improvement, and how powerful this can be when that improvement occurs frequently. For example, if a team improves 1% a week then over the course of 50 weeks (a year) they would improve by over 62%. A few days ago I had a revelation: the opposite is also true. If a team ...

Read More »

Help Managers Visualize Their Problems

I’ve been working with several managers at organizations large and small, who want to capitalize their software “earlier.” These managers have some strongly-held beliefs about the people: People are resources Resources can multitask on several projects at a time If “headquarters” does the difficult work, you can move the “grunt” work to lower wage areas and you will save money ...

Read More »

Technical Debt and Product Success

Similar to a company experiencing financial debt, products can incur “technical debt”: This happens when wrong or suboptimal architecture, technology, and coding decisions are taken. Consequently, the architecture may not be as loosely coupled as it should be, and the code may be messy rather than clean. This article explains why product people should care about technical debt and it ...

Read More »

Divide and Conquer Creates Need for Management Control

Several recent clients want help with these problems: Estimation isn’t accurate. Because the estimation isn’t accurate, management can’t predict when they can release anything. Managers can’t manage the capitalization (a way to move from expensing software to capitalizing it). Teams can’t seem to ever deliver a finished feature. The work in progress everywhere is quite large. Production support overwhelms the planned ...

Read More »

How to maximise the work not done

Recently, due to a new exciting engagement, I have been thinking a lot about simple ways to explain the advantages of iterative incremental delivery over big bang releases. When speaking to C-level executives, coaches like me often have very little time, so we need to be able to engage with language they understand to make those few minutes count. Money ...

Read More »