Articles published in February 2013

Enterprise Transformation to Agile with ISO Compliance

Enterprise Transformation to Agile with ISO Compliance

Introduction An IT consulting company with two office locations and 100-plus people specialized in custom software development and testing services. The firm did in-house software development training for developers at both locations and had trai...

Seeing the World Through Agile-Colored Glasses

Seeing the World Through Agile-Colored Glasses

There are many misconceptions about what Agile means. Here are a few of the most common that I've heard: Agile is a development methodology. Well, not really, but there are a group of methods that can all be considered Agile. Agile is the same...

Iteration Retrospective Activity: Turn the Tables

Iteration Retrospective Activity: Turn the Tables

Introduction One of the biggest challenges of a ScrumMaster is to conduct retrospectives. Running one retrospective is easy: Every conscientious ScrumMaster most likely has read the retrospective bible, Agile Retrospectives: Making Good Teams Gr...

From Problem Space to Solution Space: Why Agile Rituals Matter

From Problem Space to Solution Space: Why Agile Rituals Matter

For last few years, we've been using Agile methods such as Scrum and XP in our projects. As a team, we've gained a lot in terms of productivity, client involvement, frequent feedback, and many more benefits. But one most important change that I've...

Self-Organizing Teams: Caution, Anti-Patterns Ahead

Self-Organizing Teams: Caution, Anti-Patterns Ahead

"Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done." "The best architectures, requirements, and designs emerge from self-organizing teams." These are the two Agile pr...

Software Craftsmanship and Empowerment

Software Craftsmanship and Empowerment

Introduction When was the last time you wrote a code that was not protected with unit test/refactoring? When was the last time you fixed a bug reported in a legacy code base that was full of bad code? When was the last time you saw a class with m...

The Case for Poker Cards in Sprint Planning

The Case for Poker Cards in Sprint Planning

During sprint planning in Scrum, the team can use poker cards as a unit of measure for estimating the overall size of a user story, feature, or even associated piece of work.This tool helps the team assign points, in a relaxed manner, to stories o...

Bidding a Fixed-Price Project

Bidding a Fixed-Price Project

This is the one question Agile teams are always asking each other, and I see many questions in blogs related to it as well. How do we bid on a fixed-price project? It's a question I asked myself for a long time. Finally I've found a solution &mdas...

Scrum: The Unity of Knowing and Doing

Scrum: The Unity of Knowing and Doing

Human beings have two basic kinds of capabilities. One is knowing, including learning, making decisions, and planning. Making decisions and planning are based on using past experience to judge the future. The other capability is doing, including e...

The Case for a Technical ScrumMaster

The Case for a Technical ScrumMaster

When I first heard of the concept of Scrum nearly ten years ago, the role of the ScrumMaster seemed pretty easy to understand: a person who spent 50 percent of the time doing the same work as the team and 50 percent of the time enforcing the proce...

Displaying results 1-10 (of 16)
 |<  < 1 2  >  >|