To all PMBOK, PMP and PMI people: you are missing 1 million points! Stop trying to explain something you don’t understand!

The traditionalists are starting to be quite dangerous in the hostile “take over” of Agile and Scrum (Kanban can’t be far behind). In this post Glen tries to tell us that it is ok to call “project management” what we do in a Scrum (f. ex.) development effort. Now, that …

Read More »

Can Scrum and Kanban be used for non-software development work?

Can Scrum or Kanban be used to manage any other work than software development? Do the same concepts apply? The past week-end there’s been some chatter on twitter about using Kanban or Scrum for managing work outside the software development realm. People seem (pleasently) surprised that it can be done. …

Read More »

A feature team needs more than a cross-functional group!

In a conversation with a friend we identified an anti-pattern that can often happen to “feature teams”. Feature teams are supposed to be cross-functional groups that focus the software development process in valuable-chunks of work, which normally cross the whole system (vertical slices of the system).[1] There’s a way in …

Read More »

Why specialization in Software development is bad for business

Specialization in software development hurts our business! I’m not talking about the kind of specialization that leads to spend some more time in one area than in others. I’m talking about the specialization that leads us to have Database Administrators (DBA) or Database Designers (DBD) or Kernel programmers that don’t …

Read More »

Marketing fail redux, the Agile Process edition

I was reading a web-site from a “well know” process person/company in the software field (which will remain unnamed) and found the following quote (names changed to protect the guilty): XYZ corporation senior management decided that ABC Unified Process is the way for better quality, higher productivity and lower cost. …

Read More »

The curious case of buttoned-up Benjamin

Benjamin works in a consulting company where there was no dress-code unless the client would have a dress-code. Since most consultants were testers and coders (and you know how we dress) the clients understood not to demand a formal dress code. Then Benjamin’s company changed his boss. The new boss …

Read More »

Tactile sprint planning

A good friend of mine, James Cooper shared with me this idea about tactile planning. What is it? I asked, he explains it below, but shortly: a great way to get the team to “love” sprint planning! Tactile Sprint Planning explained One of the mantra’s I’ve always liked in Agile …

Read More »