The Science Behind Scrum

Scrum is a flavor of agile software development. In agile the development teams are cross functional and are self-managing. The development cycles, called sprints, are short, 4 weeks or less. By the end of a sprint the code must be functional, tested and working. Scrum functions on something called empirical process control. Traditional software development (command and control) uses defined process control, which is based on the theory of how something should work. This is at the heart of why so many traditional software projects either fail or generate bad code. A defined process control is meant to work on projects that are not very complex, tasks that do not need to be exact, like making hat pins. Empirical process control is used in serious engineering when tolerances need to be exact.
Read More

Do You Have Vendors or Partners?

How do you treat your vendors? Are they partners that are interested and engaged in your success or just a resource you use as needed? Many companies are too focused on having the upper hand and squeezing every last dollar out of vendor relationships. Both customers and vendors are guilty of this. When a relationship is focused on money and status, the rules change. If vendors gave their best price on the first quote and companies didn’t try to squeeze them, they could get money out of the way and focus on results.
Read More

It's Just Our Culture

Does your company know why it does what it does? Is there a good reason for all of the policies you follow? In most organizations, the answer to both of these questions is no. Here’s a test. Open up your HR manual and look at the section on sick days or paid time off. How many days do you get off for sickness? Can you use that time to take care of a family member or for a “mental health” day? Do you need a doctors approval to return to work?
Read More