They say there are three important characteristics of real estate: location, location and location. The same is true for scrum teams. Where scrum team’s members are located has a profound effect upon success and productivity. Agile advocates recommend collocation of a software development team and proximity to the customer.
Blogs on Scrum and Agile Project Management
So much of what is written about leadership is hogwash. There’s no recipe to follow. It starts with you and a belief in yourself. A belief in new possibilities. A belief in your abilities to make changes in the world, and an appreciation that you can’t do it all on your own: Leadership is a State of Mind
This blog post is about how to improve software project estimations by breaking tasks into sizes no larger than one productive day.
Risk management is a central part of traditional project management and is included as one of the knowledge areas in the Project Management Institute’s (PMI) body of knowledge. In many of my classes, participants ask how Scrum and agile address risk management. Some are concerned that agile or Scrum ignore risk management completely. This post explains how to manage risk on agile projects with the risk burndown chart.
“Excuses Might Be the Response, Not Necessarily Resistance” is an interesting blog post on how people are unable to change the way they work.
Sometimes Daily Scrum Meeting are not working. The meetings don’t release the power of the team get together in a “Scrum”. This blog post contains a list of smells to detect bad daily stand-up meetings.
This post presents what is successful project management and reasons for the popularity of Scrum.