Posts

Showing posts with the label change

Essential Scrum Metrics

Image
Some of my most rewarding professional experiences have been in leading teams through Agile transformations, adopting scrum. I've guided not only engineering teams through this transition, but even business and operations groups such as the archivists at a major media company. Very early at a publishing company a supervisor told me that "we won't do Agile" because people with our brands "need deadlines." He believed that Agile meant 'loosey-goosey' and inefficient. He also believed that we wouldn't get good metrics from a scrum team. That's definitely not the case, and in this piece I'll provide a brief overview of 3 metrics that I believe should be observed and reported. First, the sprint and release burndown will provide a view of the team's progress at a glance. This chart is a representation of the effort remaining over a period of time, and if updated on a daily basis it can help the scrum master to predict whether the team will ...

Objections to Change

Image
"Progress is impossible without change; and those who cannot change their minds cannot change anything" ― George Bernard Shaw "All change is not growth, as all movement is not forward." — Ellen Glasgow It happens when I kick off a project that will alter existing processes. It also happens when I introduce Agile to teams. Whatever the scenario, human beings are creatures of habit, and so when change is brought up, dread, anxiety, and resistance are usually the immediate reaction. The good aspect of this is that not all change should be accepted. Establishing a rule that all office photocopies have to be documented on a shared document, including number of pages and purpose, is likely to get a lot of pushback. It represents a lack of trust in employees, and creates additional work for them as well. Anyone would be right to argue against such a rule, perhaps advocating for a guidelines quantifying what would be considered excessive use, and asking people to be respo...