The Latest

Many organizations struggle with transforming from the old-style specialized silos of skills into agile teams with generalized specialists. Without this pivot, we get sub-optimal agile/Scrum environments. Howard Deiner describes what can go wrong when integrating testers properly into an...

The question of how much design to do up-front on a project is an engaging one.  Too much design often results in overkill, complexity, and wasted effort. Too little design results in insufficient system structures that require later rework, additional complexity, and wasted effort.

Agile discussions often focus on stories, backlogs, development, and testing. At Experian they also brought product strategy management and strategy into the agile fold to ensure their teams were in lock-step with customer requirements and priorities. That resulted in the delivery of...

Your organization is embracing agile. When it comes to adopting the process, your team seems to be doing all the right things. Yet deep down, something still doesn’t seem quite right. As their leader, it could be that you haven’t figured it out either. Perhaps your team is lacking some...

How do you properly compare the quality of two or more software deliverables without an accurate normalizing metric? The answer: You can’t. Example: If project A has one-hundred defects and project B has fifty defects, do you automatically assume project B is a higher quality deliverable?

Agile methods have gained the attention of leaders as a way to speed time to market and increase motivation. Businesses are looking to agile as a way to achieve organizational change so teams deliver more value faster, and where people’s pride and joy of work are enhanced.

According to studies, 64 percent of features in systems are rarely—or never—used. How does this happen? Today, the work of eliciting the customers' true needs, which often remains elusive, can be enhanced using data-driven requirements techniques. Brandon Carlson describes why traditional...