Agile Zone is brought to you in partnership with:
  • submit to reddit
George Dinwiddie03/07/14
5690 views
0 replies

What does it mean for an estimate to be right?

If we choose conformance to actuals as the definition for the “rightness” or “goodness” of an estimate, we’re certainly encouraging overestimation. It’s easier to overestimate and then waste effort as needed to be “accurate” than to underestimate and try to hit a possibly impossible target. Those who ask for estimates using this definition know this, so they are likely to arbitrarily cut the estimate in order to put pressure on development and prevent padding.

David Green03/07/14
11501 views
11 replies

Why shouldn't I test private methods?

Why shouldn’t you test private methods? Because the fact you’re asking the question means the method shouldn’t be private – it’s a piece of independent behaviour that warrants testing. The hard choice, the design decision, is where you stick it.

Avishek Sen Gupta03/06/14
5561 views
0 replies

Advice for the New Tech Lead: The Realities of Distributed Development

Let’s face it; not everyone has been there and done that, when it has come to Distributed Development. And if you have, there is a high probability that you were probably in a distributed team, you mostly worked with one group or the other, but not both. These words I will probably keep repeating in the future, but I’m not apologising for them: Never be Complacent.

Benjamin Ball03/05/14
10776 views
0 replies

DZone Weekly Link Roundup (March 5)

This week in the link roundup: Intel joins the smartwatch arms race with a $100M purchase, Facebook looks to go into low-orbit, Flexcoin shuts its doors, PHP gets a renaissance, a programmer finally admits his limitations, we learn that God created the universe on Rails, and Jurassic Park comes to your browser.

Mike Cottmeyer03/05/14
6795 views
0 replies

Don’t sell me agile, solve my problem

A wise, retired CIO told me, “Don’t sell me your solution, solve my problem.” That statement further solidified my belief that I am not “implementing agile” (hang with me), but rather I am solving a problem or a set of problems that commonly occur in enterprise environments.

George Dinwiddie03/05/14
4605 views
0 replies

Tracking Agile Velocity

It’s very common for organizations to track the velocity of the Agile teams over time. This is quite a reasonable datapoint to plot. Combined with other data, it might give you some insights when you look back, and insights based on data are typically more useful than insights based on opinion. Remember, though, to keep in mind what the data is, and what it is not.

Nathan Slippen03/05/14
2321 views
0 replies

Scaling Agile for Enterprise: Biggest Mistakes and How to Avoid Them

Applying Agile methods to an organization on an enterprise level can be difficult. In order to ensure product quality, minimal time-to-market and increased value, avoid these mistakes when embarking on this transformation.

Mike Cottmeyer03/04/14
7254 views
0 replies

Compensation Strategies for Agile Teams

The key challenges around compensation, at least for me, center around figuring out how to reward individual performance without encouraging internal competition, local optimization, or one person feeling rewarded while another feels punished. You want compensation to motivate people, not to have a negative impact on performance.

George Dinwiddie03/04/14
3480 views
0 replies

Getting so much better all the time!

Agile software development is not about productivity; it’s about working well. Yes, I think there are potential gains in productivity for most teams. Even then, the bulk of the gains are from “maximizing the work not done” rather than becoming more efficient programmers.

Edmund Kirwan03/03/14
3847 views
0 replies

Dependency inversion: the structure logarithm.

Old crotchety principles sometimes surprise. The dependency inversion principle has long earned respect from programmers for its prowess at smashing the rigidity and fragility of otherwise un-lubricated systems.

Rob Galanakis03/03/14
4683 views
0 replies

Being amazed by software development

I am continually amazed by the state of software development. I am amazed at how broken things seem to be, and I’m amazed at what powerful tools we have to fix things.

Lukas Eder03/03/14
1821 views
0 replies

How to Eliminate Bugs Through High Cohesion

Intuition tells us that methods like these ones suffer from a distinct code smell.

Tribhuwan Negi03/03/14
1534 views
0 replies

Don't Get Lost in Agile Ceremonies

Create and manage continuous improvements teams and communities within organization to fuel your agile initiatives.

Ian Mitchell02/28/14
4510 views
0 replies

Choosing Metrics for Agile Practice

In this article we look at how and why an agile team should gather elementary metrics, including lead time, throughput, velocity, and burn. We also look at cumulative flow, and briefly consider why the "actionable metrics" of the Lean Startup movement are so important to business.

Dave Fecak02/28/14
3798 views
0 replies

When You Can't Compete on Salary: Tech Talent On a Budget

When trying to hire developers, startups and small companies now find themselves in the unfortunate predicament of having to directly compete with the unlimited resources and mass appeal of market heavyweights like Google and Facebook.

Michael Täge02/27/14
6037 views
0 replies

Reporting bugs in a precise and readable way using Fail-Stories

UserStories and Scenarios used in agile methodologies are an excellent and easy-to-use way to gather requirements and to define the expected behaviour of the system in a precise and readable manner.

Mike Cottmeyer02/27/14
6566 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
3278 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
11057 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
5297 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
5297 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
3994 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
5131 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
6612 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
5034 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.