• submit to reddit
Roman Pichler01/11/13
0 replies

The Product Ownership Test

Owning a product sounds great. But what does it mean? How can we test if an individual or team owns a product?

Zac Gery01/10/13
0 replies

Finding Lost Time in Software Development

Parkinson's Law states "work expands so as to fill the time available for is completion." It was coined back in 1955 by Cyril Parkinson in The Economist. Everyone has had first hand experience with this concept. Starting a day with high expectations of productivity and losing it in the warm of a summer afternoon.

Abby Fichtner01/10/13
0 replies

Agile for Startups (MIT Guest Lecture Slides)

MIT’s Entrepreneurship Center asked me to give an Agile Product Management workshop for their Hacking IAP course. The course is a special seminar in management they’re doing for MIT student entrepreneurs.

Jurgen Appelo01/10/13
0 replies

The Problem of Top-Down Goals

I strongly suggest that organizational layers are aware of each other’s purposes. Employees should subscribe to the purpose of the organization, while the organization must recognize the needs of employees.

Chris Spagnuolo01/10/13
0 replies

Are you listening?

I think that today, it has become commonplace to value the sound of our voice and our own opinions over those of others. Most people want to be heard more than they want to listen to others. We do it in meetings, on our blogs, on Twitter. It's all about us isn't it?

Abby Fichtner01/09/13
0 replies

Hypothesis-Driven Development

You’ve also got a ton of unknowns and uncertainty. You know you can’t just go build it and hope they will come. You have to do it iteratively. Put a little bit out there, see how people react, figure out what to do next.

Venkatesh Kris...01/09/13
0 replies

4 Agile Teams to Avoid

The Sinking Ship team, The Roller Coaster team, the Well-Oiled Machine team, and the Merry-Go-Round Team. These are the 4 types of Agile teams you need to avoid.

Chris Spagnuolo01/09/13
0 replies

ScrumMasters: Don't be a Fixer

I think one of the best aspects of agile development is the ability for a team to frequently learn from their mistakes. It's especially crucial that this happens in a blame free environment.

Rodrigo De Castro01/09/13
0 replies

3 Great Articles on Technical Debt

These three articles are must-reads if you're passionate about quality and have seen or heard some of the issues mentioned in these materials.

Jim Bird01/08/13
19 replies

Why Scrum Won

Today a few shops use Extreme Programming, including most notably ThoughtWorks and Industrial Logic. But if you ask around, especially in enterprise shops, almost everybody who is “doing Agile” today is following Scrum or something based on Scrum. What happened?

Bob Hartman01/08/13
0 replies

Agile Practitioners Aren’t Supposed to Use Flamethrowers – Are They?

Most of us have not been in a literal flamethrower war, but some of us have been in our share of them in the virtual world. I may be showing my age, but we used to have a phrase for arguments on message boards: flame wars or flaming.

Chris Spagnuolo01/08/13
0 replies

Know Your Users - Create Personas

If you create a persona for each one of your user types and start using their names in your user stories, you'll start feeling more connected to your users. They won't be a generic mass out there anymore. You'll be developing software for somebody.

Jurgen Appelo01/08/13
0 replies

The Problem of Stakeholder Focus

We have to realize that everyone is entangled in a web of economic dependencies, and therefore the purpose you choose for yourself should somehow generate value for the others around you.

Giorgio Sironi01/07/13
0 replies

Caring about build files

When a build file is getting hundreds of lines long, what you can do to simplify it and why you should do it? In this article we'll see some examples of what you can usually improve in Phing build files, PHP's version of Ant.

Jim Bird01/07/13
0 replies

Classic Mistakes in Software Development and Maintenance

These simple, stupid mistakes add up over time to huge costs, when you consider that maintenance makes up between 40% and 80% of total software costs. Like the classic mistakes in new development, mistakes in maintenance are obvious and fixable.