Agile Zone is brought to you in partnership with:
  • submit to reddit
Mike Cottmeyer02/27/14
6498 views
0 replies

Managing Risk and Uncertainty in Agile

Okay… let’s set a little context here. In my last post we talked about two different types of projects. The ones that are knowable and the ones that aren’t knowable. Projects where it makes sense to estimate and projects that are more like R&D investments where we are spending money to learn and discover. Today, I want to talk more about the first kind. The ones where we do have some idea of what we are building and the technical challenges that might be involved.

Johanna Rothman02/26/14
3232 views
0 replies

Cost of Delay: Why You Should Care, Part 6

I’ve outlined five potential costs of delay in the previous five posts. The real problem is this: Why should you care? Maybe you have a “sweet spot” in the way you start your projects or release them. “It just takes that long here.” (That’s the sign of a system impediment.)

Gil Zilberfeld02/26/14
10949 views
4 replies

Product Roadmaps Are Anti-Agile

I was listening recently to the “Global Product Management Talk” live podcast (which I recommend, by the way). The speaker talked about creating roadmaps for product lines. It’s an interesting topic for me, as I’m juggling between products everyday. As the the interview sped along, I asked on Twitter: How are roadmaps related to agile?

Vijay Narayanan02/26/14
5241 views
0 replies

With Reusable Components Think Extend and Integrate

Many systematic reuse initiatives don’t take off the ground because of the over-emphasis on investing in a new set of components. There is all the talk and promise of enhanced productivity, reduced cost, and swift time to market – however, as focus shifts to building a library of components, real delivery suffers and business applications don’t see any material improvements.

Vijay Narayanan02/26/14
5241 views
0 replies

With Reusable Components Think Extend and Integrate

Many systematic reuse initiatives don’t take off the ground because of the over-emphasis on investing in a new set of components. There is all the talk and promise of enhanced productivity, reduced cost, and swift time to market – however, as focus shifts to building a library of components, real delivery suffers and business applications don’t see any material improvements.

Ian Mitchell02/25/14
3925 views
0 replies

Choosing Columns for Agile Team Boards

In this article we answer a common query about Scrum and Kanban boards: what columns should be used for tracking the progress of work items?

Dave Bush02/25/14
5075 views
1 replies

Test Driven Specifications

The gig that was suppose to be a couple of weeks long was quickly turning into a perpetual job. Soon I learned that what I was working with was a system that had a lot of bugs, but no one was willing to admit that. Eventually, frustrated by the fact that this system seemed to have a new bug every day, I asked for the specs so that I could create a test plan. That’s when I found out the worse news of all about this system: Lost Specifications.

Kin Lane02/25/14
6555 views
0 replies

Why Are We Not Innovating On The Big Problems?

One side of my news feed showcases how we are innovating with technology in so many new ways, and the other side just tells how screwed we are. Which is it? Are we innovating or are we drowning in big problems?

Eyal Golan02/25/14
4949 views
0 replies

Agile Mindset During Programming

The problem I had was that I knew were I needed to go, but instead of taking small steps, I kept trying to take one big leap at once. Which brings me to the analogy of Agile to good programming habits (and TDD would be one of them). One of the advantages in Agile development that I really like is the small steps (iteration) we do in order to reach our goal.

Michael Sahota02/24/14
2971 views
0 replies

Beyond Roles in Scrum

In this post we will explain how we can move to shared responsibility by focusing away from roles in Scrum.

Rob Galanakis02/24/14
5504 views
0 replies

Using code metrics effectively

Code metrics are a conversation starter. Metrics are a great way to start the conversation that says, “Hey, I notice there may be a problem here, what’s up?” In this post, I’ll go through a few cases where I’ve used metrics effectively in concrete ways. This is personal; each case is different and your conversations will vary.

Mike Cottmeyer02/24/14
4903 views
0 replies

Keeping Everybody Happy with Separate Agile Systems

To fully realize predictability, progress visibility and collaboration through Agile, you need separate Agile systems to manage responsibilities and accountabilities that are different for each role.

Steve Smith02/24/14
3691 views
0 replies

Organization Antipattern: Release Testing

Described by Elisabeth Hendrickson as originating with the misguided belief that “testers test, programmers code, and the separation of the two disciplines is important“, the traditional segregation of development and testing into separate phases has disastrous consequences for product quality.

Zac Gery02/21/14
7131 views
0 replies

When to Flex or Stand Firm in Programming

One bad habit that permeates the industry is fellow developers arguing about how code is written. Although their hearts are in the right place, in most cases their focus may need adjustment. The late author Zig Ziglar was known to say "Be firm on principle but flexible on method." This is an excellent approach not only to life but programming.

Abhijeet Sutar02/21/14
2258 views
1 replies

Changing Commit Message in Git

Iwas amazed by an interesting feature of git, that it allows you to edit and change previous commit messages.

Dave Fecak02/21/14
1134 views
0 replies

Counteroffers, Secrecy, and Fear

Counteroffers are a fairly common occurrence in technology and other competitive job markets, and much of what we think we know about counteroffers seems to originate from agency recruiters.

Eli Bendersky02/20/14
4374 views
0 replies

Squashing Github pull requests into a single commit

Github’s pull requests are a terrific tool for collaborating on open-source projects. I get one or two a week on average for my projects, and I love it. The UI is very clean – you get to see exactly the changes, the full branch if you’d like, even the Travis CI integration is working checking that the branch still passes your tests.

Jens Schauder02/19/14
5240 views
0 replies

Your Code Ain't Your To-Do List

What do you do if you find a problem in your code base but can’t fix it right now? If you are like many developers you probably put something like a todo comment next to it, so you don’t forget it.

Mike Cottmeyer02/18/14
5195 views
0 replies

Religion, Politics, and Agile

Most folks have heard the old adage that you never discuss religion or politics in polite company. Frankly, I’m guilty of both because I think it’s fun and I can take it. As a society, I think it’s time to consider a third category of zealotry that needs to be banned from our fancy dinner parties… agile methodology.

Michael Norton02/17/14
7231 views
0 replies

Jungle Gyms, Not Ladders

Ditch the job ladders and formal roles. Pay everyone in the company the same base salary. For each of the skills an individual can display and utilize, increase their pay by a set, published amount. I've had this in my head for years. This is the first I've put it to paper. It's not fully formed and I've never tried it. This is a concept. I suspect it is wrought with issues, but I know for certain that job ladders are wrought with issues.

Vlad Mihalcea02/14/14
4768 views
0 replies

A beginner’s guide to Git feature branches

Git makes branching a commodity and each feature can be developed in a separate branch. This is desirable since the merging process may be out of your control. If you develop on the default master default branch and a given committed feature is postponed, you will have to revert your changes prior to starting working on a completely different feature.

Rob Galanakis02/13/14
5756 views
0 replies

Can you grok Agile without a programming background?

The core question, which will continue recurring, is: can you truly understand Agile, or any development methodology, without having done that most fundamental development work: programming?

Ian Mitchell02/13/14
3355 views
0 replies

Stabilizing Teams for Agile Practice

New agile "teams" are often just people who bear some sort of relation to the work that needs to be done. In this article we look at how rigor can be drawn around team boundaries, and at the duties stakeholders must fulfil in a new agile way of working.

Mike Cottmeyer02/12/14
5287 views
10 replies

Should You Use Agile To Build Your Next Home?

Before we start our conversation about governance in the structure-governance-metrics framework we’re building out, I want to take a minute and see if I can finally tell you guys about the house my wife and I were planning to build this past summer.

Tom Howlett02/11/14
8642 views
1 replies

A Return To Scrum

I thought we’d grown out of Scrum, I admit to describing it as agile training wheels, but I’ve found a new love for it and its constraints. I’m glad I got a taste of what happens when you remove them, and perhaps there are organisations that will flourish when you do. But I wonder if there really is?