Agile Zone | Software Methodologies for Development Managers

Jurgen Appelo03/15/13
954 views
0 replies

360 Degrees Dinner - Peer Evaluations At The Dinner Table

Invite the whole team for dinner,and tell them in advance that, before or after dinner, the team will evaluate each team member's performance, at the dinner table, face-to-face. You, as a manager or team leader, will volunteer to be the first one to be evaluated.

Roman Pichler03/15/13
3647 views
1 replies

Nonfunctional Requirements

Explore nonfunctional requirements that apply to the entire product or to important features early on. This helps you create a great user experience, and make the right architecture and technology decisions.

Esther Derby 03/15/13
2504 views
1 replies

Motivation Misfires

Some managers still assume that “workers” won’t work without carrots (or sticks). It doesn’t occur to them that carrots might not be the preferred diet.

Mike Cohn03/14/13
2344 views
0 replies

Simulating a Project by Resampling Velocity

I want to talk about a technique called “resampling” that I’ve become quite fond of for making predictions about future velocity, a method for measuring the rate at which agile teams consistently deliver value.

Nial Darbey03/14/13
1631 views
0 replies

Extending Mule with DevKit – the LDAPConnector

We’ll show you the main ingredients needed in the development of a new Connector by walking you through the code of our LDAP Connector. This will allow you to connect to any LDAP server and perform every LDAP operation.

Allan Kelly03/14/13
5550 views
2 replies

Conway's Law v. Software Architecture

While Conway's Law can be seen at the macro level, the company level, it is also observed in in the small, at the micro level.

Jurgen Appelo03/14/13
2174 views
0 replies

The 60 Percent Rule

I’ve heard some coaches suggest a 60% rule: everyone should spend 60% of their time on the same team, the same department, or the same organization. The rest of their time they can spend working for others.

Esther Derby 03/14/13
980 views
0 replies

Team Trap #5: Withholding Information

I’m not talking about information related to the task and context, here, though that can damage a team. Withholding that sort of information is unacceptable, and probably pathological. I’m talking about a different sort of information: information about your internal state .

Mike Cohn03/13/13
2227 views
0 replies

Agile in the Age of Hyperspecialization

Agile does not at all require individuals to be generalists, but individuals are expected to work together as a team. The handoff-driven model created by hyperspecialization and used on sites like TopCoder are anything but agile. So where does this go?

Christian Grobmeier03/13/13
2551 views
3 replies

Fragmented Projects and Overcommitted People

Calculate the human factor into your Scrum sprint. Don’t measure your success on your overtime and switch off your mobile on weekend. You’ll be ways more productive on Monday.

David Bernstein03/13/13
1670 views
0 replies

Compromises on Quality

Far too often I hear managers say, “Just get it out the door.” I understand the perspective. We work in a world of constraints and the business needs to survive.

Mike Cottmeyer03/13/13
1501 views
0 replies

That’s Not Agile!?

Agile at the Enterprise Level is not about the two-week inspect and adapt cycle… it’s about small batches and flow.

John Sonmez03/12/13
4103 views
10 replies

7 Reasons Why You Should Tackle Hard Problems Last

We tend to think it is best to solve hard problems first, because we are thinking about eliminating our fear, not because we are thinking about what approach has the highest chance of success or is the most optimal. I call this FDD, or Fear Driven Development.

Steve Smith03/12/13
2732 views
0 replies

Testing Antipattern: Release Testing

By dissolving our release testing team into our product team, we can improve our product lead times and reap the benefits of our entire testing team being involved in the product development process.

Gil Zilberfeld03/12/13
1727 views
0 replies

The Real Enemy: Testers That Can't Program & Programmers That Can't Test

Lior Friedman asked whether a tester should know how to program or become obsolete. Lanette Creamer said the same fate awaits programmers who can’t test.