Portfolio Category: Software Development

Feb 12, 2018
Disconnected business priorities

There is often a wide gap between the priorities of projects within the development organization, the priority of the project in the view of the overall business, and the priority of the project in the eyes of the requester. A common issue is that a ‘high priority’ project for one department is not viewed as […]

Continue Reading

Feb 12, 2018
Poor communications

It is important to keep everyone in the loop on project status, but it is easy to forget to do it. This is where a lot of the mistrust between IT and the business team comes from: The business does not feel like it has a good handle on what’s happening with its projects. And […]

Continue Reading

Feb 12, 2018
Failing to account for tasks

How many times have you seen a deadline blown because it was established without accounting for a critical task like testing? That is another reason why you cannot and should not ever accept a task on a timeline that is not broken down into its component tasks. There is a chance that the estimate omits […]

Continue Reading

Feb 12, 2018
Estimating times too broadly

Another typical issue with time estimates involves not breaking tasks down into small enough pieces. If I’m told that a piece of work will take one week, I’ll ask where exactly that number is coming from. Unless someone has analyzed all the minor pieces of work in the whole, a ‘one-week’ time estimate is nothing […]

Continue Reading

Feb 12, 2018
Estimating times too far out

A common problem I see with certain project management methodologies is that they like to play ‘just so stories’ with timelines and time estimates. Project manager who honestly think they know what pieces of functionality any given developer will be working on more than a month or two out (unless it is a very large, […]

Continue Reading