• submit to reddit
Esther Derby 12/27/12
0 replies

Alternatives to Bureaucratic Hierarchy

Most companies settle for practices shaped by management thinking of the first half of the last century–without a second thought. The language of this thinking is mechanistic and dehumanizing. It’s the language of efficiency, compliance, hierarchy, rules.

Todd Merritt12/27/12
0 replies

What is Agile Modeling and Why Do I Need It?

Agile Modeling is an add-on to existing agile methodologies like Extreme programming (XP) and Rational Unified Process (RUP). Agile Modeling enables developers to develop a customized software development process that actually meets their current development needs and is flexible enough to adjust in the future.

Johanna Rothman12/27/12
0 replies

Management Myth About “No Time for Training” Posted

I have another management myth posted on Stickyminds. This one is about training. Many managers say: "Have No Time for Training”.

Tathagat Varma12/27/12
1 replies

Your Estimates or Mine

For decades now, the project management world has been divided between top-down estimation and bottom-up estimation. Both are required for a comprehensive and useful project planning, but unfortunately, most people use one over the other.

Giorgio Sironi12/26/12
0 replies

Agile traveling

We found ourselves applying Agile principles for planning our day in Rome on the go. A backlog of locations to visit calls for deciding where to go at the last responsible moment...

Mitch Pronschinske12/26/12
0 replies

The Mikado Method - Making Code Changes Less of an Impact

The Mikado Method is a simple straight forward methodology for large scale refactoring. It's a way to peel the layers of complexity away from any system. Systematically attack refactoring, in the knowledge that every change you make will be for the better of the system, rather than hoping it will be.

Jim Bird12/26/12
0 replies

You Can’t Refactor Your Way Out of Every Problem

Some people naively believe that you can refactor your way out of any design mistake or misunderstanding – and that you can use refactoring as a substitute for upfront design. This assumes that you will be able to immediately recognize mistakes and gaps from customer feedback and correct the design as you are developing.

Johannes Brodwall12/26/12
0 replies

Tell a Story with Your Project Plan

I needed to fail with modern methods for requirement gathering in order to understand old methods for requirements gathering. Many software projects write requirements in what is refered to as “user stories”. But a use story is not a story at all.

Dave Rooney12/26/12
0 replies

Agile in its Second Decade

The Agile world as it is today in 2012 is not what we learned years ago. Each year it seems that there are calls to rewrite the Agile Manifesto, a new certification scheme pops out of the ground, more automated tools are created and marketed to simplify collaboration, and we move further and further away from the values and principles that defined the movement in 2001.

Johannes Brodwall12/25/12
0 replies

Use Scrum Even if You Don’t Want to be Agile

You don’t need to “drink the Agile cool aid” to benefit from the experience of Scrum over the last 20 years. And many projects that profess being Agile just be using the rituals from Scrum within an old mindset. You will not get the same benefits from Scrum as a truly agile team, but that doesn’t mean it’s not right for you.

David Bland12/25/12
0 replies

Performance Evaluations and Scrum.

One of the most frequently ask questions that I’m asked is, how do you do personal performance reviews and appraisals in a Scrum environment. If the roles are equally balanced then who should be responsible for evaluating a team member?

Mohamed Radwan12/25/12
0 replies

What’s New in TFS 2012? My Series of Tutorials

In this series I will start introducing what’s new in Visual Studio 11 and Team Foundation Server 11 ( TFS 11) or as we expect to be Visual Studio 2012 and Team Foundation Server 2012 (TFS 2012)

Giorgio Sironi12/24/12
0 replies

Code Katas: Ruzzle solver

Ruzzle is a word game based on finding words in a 4x4 grid of letters. Solving the game automatically is the goal of the Ruzzle Solver kata.

Stephen Forte12/24/12
0 replies

Beyond Agile Estimation Part II: Improving Your Metrics

Stephen Forte continues his experiment of using a spreadsheet in his Agile Estimation efforts. After the first sprint they had an estimated time to completion of 15.14 weeks. Now we take a look at how this works after another sprint.

David Bland12/24/12
0 replies

Scrum and Fixed Price Contracts

Fixed Priced contracts don’t make a great deal of sense in a Scrum world. This is really because traditional software development and Agile software development are two different paradigms … and solutions that work in one paradigm often doesn’t make sense in another.