As a project grows the role of the guru has to change with it. At the start the guru is the technical wizard writing a lot of code because he is the entire technical team. When the project is large, he isn’t so much a coder but a coordinator and manager of the technical vision. Those are two very different sets of skills that don’t really have that much overlap.

Read the rest of this entry »

Some processes are too big, some are too small so how do you find what’s just right? A lot of people would argue that highly detailed processes with buy in from a lot of different stakeholders slows the pace of software development. The fundamental reason for “agile” methods is to cut the overhead out of the processes to focus back on delivering value to the customer. Read the rest of this entry »