Wednesday , February 21 2018

Writing Changeable Code in Test-Driven Development

Studies have shown that making changes to software is expensive, no matter how small the changes. The reason is typically that the underlying code was not written to be changeable without breaking other systems. In an article for AgileConnection, David Bernstein insists that changeable code does not take longer to write than static code. But it does require that you think with a different perspective. Change Your Mind Bernstein says this about the mindset to …

Read More »

One Reason Why Your Software Doesn’t Work

Everyone has seen the discouraging numbers on how many software projects fail, and countless fingers have been pointed in countless directions for it. In a post at Hacker Noon, Jez Halford cites one specific reason that casts no blame: “unconscious assumptions.” The Phantom Mistake Halford illustrates the idea of unconscious assumptions with this short narrative: I got married a while ago, and my wife, Jodie, took my surname. That meant she had to spend ages …

Read More »

Avoid ROI as a Basis for Prioritization

Business is all about ROI, and rightfully so, but ROI is not always a clear, concrete thing. More often—and especially before work has begun—ROI is a fuzzy, shifting thing. That makes it a difficult thing to use as a basis for feature or even project prioritization. In a post at her blog, Johanna Rothman discusses how ROI and also earned value (EV) as a basis is not right in an agile setting. Bet on a …

Read More »

What Agile Can and Cannot Do

Consistently, one of the greatest challenges of agile transformation is simply understanding what it is. Agile cannot do everything, but it can do quite a lot. The lines of division are unclear to outsiders looking in, or to those new to the methodology. In an article for Scrum Alliance, Pratik Kothari gets specific about what agile can and cannot do. The Division In scheduling, agile enables better feature development prioritization in projects, and when paired …

Read More »

7 Actions State Government IT Leaders Must Take

The government dares to dream of a day when it is hailed for its efficiency. That day is far, far off, perhaps in a quintuple-digit year, but nevertheless! In an article for StateTech, Juliet Van Wagenen shares seven actions government IT leaders can take to make for more effective agile implementations: Get CIOs to fight for agile development. Focus on building a more agile culture. Engage businesses in IT transformation. Design digital government with users …

Read More »

Your Strategic Planning Should Be Agile, Too

Agile was borne out of desire to get away from the problems that plague waterfall development, and agile is now very successful. The problem is that strategic planning at the highest levels still often resembles something akin to waterfall planning. A multi-year plan is made up front based on research examined and discussions had by a choice few people, and then everyone hopes reality ultimately lines up with the plan. However, those hopes are often …

Read More »

Recognizing the Five Symptoms of a Poor Backlog

Is your backlog a beautiful thing to behold, or does it have a face only a mother could love? Well, if you get used to ugly and disorganized, you may not be able to tell the difference anymore. So in an article for Scrum Alliance, Pratik Kothari shares five symptoms of a poor backlog incited by a struggling product owner: Poor planning Not enough detail More than 20 percent churn in objectives Features dissatisfying the …

Read More »

How to Overlap Work in Agile

Structure provides reliability, so it is no wonder why people are attracted to the idea of working in phases. But agile explicitly draws a line in the sand and insists that teams can do better than that. In a post at Mountain Goat Software, Mike Cohn explains how to forego phases and overlap work in agile. Deft Application Overlapping work reduces time to market because it ensures that no available resources are ever left twiddling …

Read More »

5 Overlooked Opportunities in Agile Estimation

Opportunity surrounds us all the time, but if we are blind to it, then it makes no difference. Are you missing opportunities during agile estimation? In an article for Scrum Alliance, Ajeet Singh describes five such opportunities: Opportunity to learn from others Opportunity to identify alternatives Opportunity to validate the story Opportunity to improve teammates’ estimating ability Opportunity to reinforce scrum values Optimistic Estimation Opportunity to learn from others occurs when individuals are allowed to …

Read More »

Envisioning a Perfect Daily Standup

Most daily standups feature the same few key ingredients, with an extra gimmick or adaptation in place here and there. It helps to swap ideas about those gimmicks and adaptations from time to time though, for the sake of keeping things fresh. In a post at his blog, James Mensch discusses some of his thoughts on how to build a “perfect” daily standup. Doing Well in the Standings In addition to the standard “what I …

Read More »