Agile Zone is brought to you in partnership with:
  • submit to reddit
Andrew Fuqua09/09/14
1 replies

Don't Estimate Stories In Sprint Planning

I don’t estimate stories in sprint planning. Nor do I re-estimate stories in sprint planning. I estimate stories in a separate estimating meeting and usually at least a couple sprints in advance, if not more. There are a few reasons why (re)estimating during sprint planning is a dangerous practice:

Allan Kelly09/09/14
3 replies

Agile outside of software

While not every Agile practice can be taken out of software development and used someplace else the roots of Agile mean that the principles, values and ideas which Agile is built on can be. In your domain Agile as now known might work quite well, but in someone else’s domain there may be more need to think deeper.

Mike Bushong09/09/14
2 replies

On building teams: experience or talent?

Obviously when you hire, you want to find a good mix of experience and talent. But a perfectly balanced straddle between the two is impossible. So when forced to choose between them, which do you choose: experience or talent?

Chris Odell09/09/14
0 replies

SOHO Agile: Is agile relevant to the SOHO developer?

Agile is often seen as a team process, and certainly agile lends itself to team activities. So can you apply agile to the Sole Home Office developer?

Mateusz Haligowski09/08/14
15 replies

Programmer, know thy tools!

On the importance on non-programming skills in the job of a programmer.

Lucas Saldanha09/05/14
4 replies

Pitfalls of Agile Software Development

In this post I discuss three pitfalls of agile software development faced by developers when trying to make changes in the development process at "non-agile" companies.

Gil Zilberfeld09/03/14
1 replies

Metrics: Good vs. Evil

In our ever going search for simplicity, metrics help us minimize a whole uncertain world into a number. We like that. But metrics are over-simplification. We should use them like that.

Johanna Rothman09/03/14
0 replies

Managers Manage Ambiguity

We can refine our estimates, if management needs them. The question is this: why does management need them?

Andrew Fuqua09/02/14
0 replies

Flow Is For Sissies

The moral of the story is that real options thinking, systems thinking and many other such concepts present or yet to come may be more appropriate in some cases than Lean/Kanban thinking. Lean/Kanban thinking is useful, but it isn’t all there is.

Rob Galanakis09/02/14
1 replies

Hire talented people and get out of their way?

Today's quote is: "In most cases being a good boss means hiring talented people and then getting out of their way." This advice (hire smart, don’t micromanage) is so simplistic, it’s hardly worth saying. The profound stupidity is equating this with “being a good boss“. No, hiring smart people and not micromanaging them is the absolute, bare minimum you should be doing as a boss.

Allan Kelly09/02/14
0 replies

Book: Scaling up Excellence

Right now I want to blog about a book because I want to recommend this book. The book is: Scaling Up Excellence by Robert Sutton and Huggy Rao. I hope this book becomes more widely known in the software development community, and particularly those concerned with “Agile” and “Scaling Agile.”

Robert Diana09/01/14
0 replies

Programming Languages Job Trends: Part 2 - August 2014

In part 1 of the programming language job trends, we reviewed Java, C++, C#, Objective C, and Visual Basic. In today’s installment, we review trends for PHP, Python, JavaScript, Ruby, and PERL. Watch for part 3 in the next few days, where we will look at some emerging languages and others gaining steam.

Gerry Claps09/01/14
0 replies

3 Simple Steps to Effective Retrospectives

Do you create a list of actions by analyzing the data you collect in your Retrospectives? Read on for 3 simple steps on how to run your Agile Retrospectives.

Curtis Lassam08/30/14
0 replies

Cube Drone #3: Coffee

From software developer Curtis Lassam (who writes about comics and code) comes a comic series called Cube Drone. This is Cube Drone #3: Coffee.

Gil Zilberfeld08/29/14
4 replies

Superman vs. Batman: The Agile Version

I used to be Superman. I could do anything I wanted, and no one would tell me I was wrong. But Superman can be wrong. And when Superman makes a mistake, it can be a crucial mistake for the organization. In short, we don’t need Superman. We need Batman and Robin.

Johanna Rothman08/29/14
0 replies

Capacity Planning and the Project Portfolio

If you are considering doing capacity planning on what the teams can do based on their estimation or previous capacity, don’t do it. First, you can’t possibly know based on previous data. Why? Because the teams are interconnected in interesting ways.

Alex Curylo08/29/14
0 replies

Project Management: Kanban

So chances are that, should you follow any kind of formalized project management, it’s likely to be a form of Scrum. And if so, we’ll just betcha that you’ll nod along with this piece:

Bob Hartman08/29/14
0 replies

Agile Denver Session Notes: Unscaling

For those who attended this week's Agile Denver meetup, here are the slides and some additional resources for you…

Mike Cottmeyer08/27/14
0 replies

Why Iterative Planning?

Planning and elaboration go hand in hand as items move from unknown problem -unknown solution to known problem-unknown solution to known problem – known solution.

Venkatesh Kris...08/27/14
0 replies

Measuring Business Value in Agile Projects

During backlog creation, user stories need to be compared and contrasted in order to promote maximum value delivery. The product owner might need to use different techniques, such as T-shirt sizing, in order to better prioritize the project’s stories.

Dave Rooney08/27/14
0 replies

"How Thin is Thin?" An Example of Effective Story Slicing

Like the graphene example at the beginning of the post, thin stories have remarkable properties far beyond the fact that they are just "thin". The value gained by learning how to split Stories effectively is enormous owing to the flexibility it provides by deferring decisions as long as possible and the removal of the need to estimate at a granular level.

Rob Galanakis08/25/14
1 replies

The low status of software engineers

Bill had two very different experiences interviewing for two different positions at two different companies: one as a software engineer, and one as a VP-level manager.

Bob Hartman08/25/14
0 replies

Scrum Basics: When Should We Schedule Sprint Transitions?

For a one week sprint, it’s possible to do Review, Retrospective, and Planning all on Wednesday morning.

Ian Mitchell08/25/14
0 replies

Counting Chickens: Undone Work in Scrum

By definition, any work that has not been completed to the satisfaction of the DoD remains undone. Taking work off a Product Backlog just because it is on a Sprint Backlog is therefore precocious and a mistake.

Curtis Lassam08/23/14
0 replies

Cube Drone #2: Nyan

From software developer Curtis Lassam (who writes about comics and code) comes a comic series called Cube Drone. This is Cube Drone #2: Nyan.