Agile Zone is brought to you in partnership with:
  • submit to reddit
Jurgen Appelo05/06/13
1082 views
0 replies

Ring the Bell!

When the sound of the ship’s bell blared through the office, all employees immediately got together for a 10-minute celebration. Our people knew that the bell was often a signal for free cake or cookies, which probably contributed to the quick and easy gathering of the entire work force around the coffee machine.

Kane Mar05/06/13
4019 views
0 replies

5 Big Scrum Questions – Issue 4

This is the final issue of James Brett‘s 5 Questions. Issue 1 featured Ron Jefferies, Issue 2 featured Ken Schwaber, and Issue 3 featured Mike Cohn. In issue 4 of the five questions series we hear from Alistair Cockburn.

Olga Kouzina05/06/13
2054 views
0 replies

Joy Spring and Estimated Deadlines

Even Phil, the Groundhog, screwed up with his estimate, and while the spring is already far in, it’s high time to come up with a very fitting narrative of what missed deadlines, and deadlines in general, are about.

Martin Fowler05/05/13
6866 views
1 replies

"How do you estimate on an Agile project?" by Martin Folwer and ThoughtWorks

If you’re interested in techniques for estimation, you should take a look at this pdf ebook. It contains half-a-dozen essays on estimating in agile projects, drawn from our experiences with a wide range of clients. We explain approaches based on story points and on story counting, which should give you a good overview for you to explore an approach that will work for you.

Kane Mar05/05/13
3251 views
1 replies

5 Big Scrum Questions – Issue 3

This is the third issue of James Brett‘s 5 Questions. Issue 1 featured Ron Jefferies, and Issue 2 featured Ken Schwaber. From the first issue of 5 Questions ”The ideas was to ask five specific questions to members of the Scrum community and post the their replies.”

Mahdi Yusuf05/04/13
2723 views
0 replies

Remember to Experiment

Take a fresh look at problems, don’t go through your mental catalog of past problems. Each problem is unique and it has its own set of unique solutions. You might surprise yourself, with what you come up with.

Jurgen Appelo05/04/13
2779 views
0 replies

Emphasize Good Practices and Don't Punish Mistakes

In many working environments people’s focus is usually is on fixing problems. This makes sense, because continuous improvement allows organizations to survive and thrive.

Martin Hinshelwood05/03/13
7671 views
3 replies

Not Using Test-First? You're Doing it Wrong.

If you look up Test First on Wikipedia you will be redirected to the Test Driven Development (TDD) page and I believe this to be incorrect. While TDD is one, arguably the most effective, form of Test First it is by no means the whole thing.

Ian Mitchell05/03/13
3311 views
0 replies

Agile Estimation in Practice

Out of all of the agile practices which have been adopted in recent years, few have proven more controversial than estimation. To estimate, or not to estimate? That is the question. In this article we look at the reasons for disagreement and the circumstances in which estimation can make sense.

Johanna Rothman05/03/13
1308 views
0 replies

Personal Kanban and Iterations, Day 4

I’m using my kanban to help me to get to done on my tasks, not to track my every piece of work. I’m using it to not forget work. I have a couple of phone calls this morning and a phone call this afternoon. I hope to complete one of the workshops today. Maybe.

Christopher Taylor05/03/13
1055 views
0 replies

Management, Dark Arts, and Disguises

People usually think of the pawns as the most disposable pieces, but great managers don’t use them as strategic sacrificial lambs for their own gain. Trying to keep all the pieces on the board becomes an unacknowledged and thankless part of the manager’s job.

Tom Howlett05/02/13
3422 views
2 replies

Assumptions Were Made for Testing

The Oxford Dictionary defines an assumption as: “a thing that is accepted as true or as certain to happen, without proof”. We constantly make assumptions. Sometimes we are aware of them, often we’re not.

Johanna Rothman05/02/13
3218 views
0 replies

Personal Kanban and Iterations, Day 3

I’ve been busy crossing work off my list. And, as with all of us busy people, I’m adding more work to my list. I feel as if I’ve accomplished a lot this week.

Mitch Pronschinske05/02/13
1309 views
0 replies

Dependency Inversion Principle in the Wild

The Dependency Inversion Principle (DIP) has been around since the early '90s, even so it seems easy to forget in the middle of solving a problem. After a few definitions, I'll present a number of applications of the DIP I've personally used on real projects so you'll have some examples from which to form your own conclusions.

Gil Zilberfeld05/02/13
3327 views
0 replies

I Have An Idea!

The biggest waste in software is what we build and isn’t used. Since we can’t know in advance what will be a selling feature, we have to implement the feature, put it in the wild, and hope for the best.

Johanna Rothman05/01/13
8508 views
2 replies

Personal Kanban and Iterations, Day 1

I use a form of personal kanban inside one-week iterations to finish my work and notice what I am not doing. I do this to maintain a cadence of blogging and to finish work. Did you notice that word, finish?

Paul Hammant05/01/13
2820 views
0 replies

When Agile Meets Angular and UX-led Development

UX-led development is where your User eXperience (UX) developers are active within a dev-team, pushing the experience, behaviors and interactions. Pushing in this context means rapid evolution of a working UI.

Jay Fields05/01/13
2991 views
0 replies

Year Five

The average lifespan for a software engineering job is 4 years. Okay, I've never actually seen proof (or contradiction), but that's the general feeling in the groups I associate with. Perhaps that's selection bias - my employer has generally changed on year 3 or 4.

Johanna Rothman05/01/13
2793 views
0 replies

Personal Kanban and Iterations, Day 2

And, since I’m cheating on how to do a real personal kanban, I thought I would at least describe for you how to do real personal kanban over at Personal Kanban for Your Job Hunt.

Sean Hull04/30/13
2556 views
0 replies

I Thought Sales Sucked, Then I Gained a Business Perspective...

The sales team made promises of technology the company wasn’t capable of delivering. Meanwhile the engineering team was sent scrambling to answer to those promises. This is why I started out hating sales in my early career.

John Sonmez04/30/13
1614 views
0 replies

How To Deal With Making Mistakes

It is to easy to get hung up on a mistake and become paralyzed by it in such a way that it prevents you from having future success. I seem to have an instinctual desire to throw away what I am doing or try to completely wipe the board clean, whenever I make a mistake.

Ian Mitchell04/30/13
1295 views
0 replies

Sprint Planning in Practice

The beginning of a Sprint provides a new opportunity for getting things right. Unfortunately, Sprint Plans are easily stomped on by operational concerns. Emergencies, defect fixes, new priorities that trump earlier ones...the list of potential spoilers for a Sprint Goal seems limitless. Is Sprint Planning really worthwhile, or is it a ticket to nowhere?

Roman Pichler04/30/13
1598 views
0 replies

Agile Scenarios and Storyboards

Scenarios and storyboards are great tools to describe how users interact with a product. They also complement user stories nicely: Scenarios and boards help explore risky stories, discover new user stories, and capture the relationship between stories.

Martin Fowler04/29/13
4149 views
0 replies

The Component Test

A component test is a test that limits the scope of the exercised software to a portion of the system under test. It is in contrast to a Broad-Stack Test that's intended to exercise as much of the system as is reasonable.

Jim Bird04/29/13
5082 views
0 replies

Code Ownership – Who Should Own the Code?

A key decision in building and managing any development team is agreeing on how ownership of the code will be divided up: who is going to work on what code; how much work can be, and should be, shared across the team; and who will be responsible for code quality.