Experience Matters

I recently attended a PMI event on the age old question of what makes a project more successful than another. The discussion started by stating the obvious need to focus on the 5 W's, but also the importance of 'how' things are done. The discussion was primarily philosophical, asking us to each think of the differentiators. There isn't a one size fits all approach to success, and while checklists and "best practices" are helpful, I believe it's the team's application and foresight that goes into the application of a tool or method that determines success. Sure, guidance from other sources... Read More»

Getting Back to Basics

A few months ago I wrote about companies and users thinking they need a software system for everything under the sun. I continue to be amazed at how many managers and businesses think they cannot take on certain projects or even perform their jobs to the fullest, without software. What did companies do 30, 40, or 50 years ago? Did we just tell our managers we can't do certain things because they are too complex or we don't have the proper tools? That's doubtful. Granted, the business challenges we face today may be more involved than they were years ago,... Read More»

Professional Gratitude, Recognition & Growth

While I always try to reflect on events as they occur; I realized this month that I could do more to "live in the moment" and reflect on professional lessons more regularly. Being so rushed and driven can certainly mean getting more done, but it can also result in glossing over some rich and meaningful encounters and the corresponding growth. While we may not always look at our professional interactions as something to be grateful for, we should. The people, projects and experiences we have in our professions shape our future, allow us to grow and allow us to shape... Read More»

Rescuing Projects - Part II (the Informal Method)

Last month I wrote about formally rescuing projects where someone officially turns over the project to you. There are other, less direct ways in which you can be asked to help save a project. These requests and pleas for help can put a strain on the team dynamics, our relationship with our peers and other stakeholders. Following the guidelines below will help mitigate these issues and help keep your relationship in good standing. Phrasing - Instead of having your management team (and yourself) state things like "Mary will now be managing the project", soften the language by using statements like... Read More»

Rescuing Troubled Projects: Part I (the Formal Method)

Projects that are not performing as planned can be cancelled or if there is enough earned value and if the expected return is high, they can be rescued. I've been a part of many rescuing efforts for colleagues and know our first reaction may often be one of inquisition. However, instead of viewing this situation as another layer of inheritance and more work, you can turn the situation into an opportunity to show your organization and customers the power of applying sound PM methodologies. While you may start to see an increase in requests for your expertise, it is our... Read More»

Don't Fall Into the Order Taker Trap

Lately I have noticed an increase in businesses and industry experts requesting their customers tell them exactly what they want, how it should be delivered and so on. These businesses range from retailers to highly respected, professional organizations. In general I believe you get what you pay for but have been amazed at how often this seems no longer the case. I'm often surprised that any business, especially a professional service organization would ask their customer to lay things out in such detail. What ever happened to analysis and being experts in our specialties? When we outsource or call on... Read More»

Keeping the Band Aid Affixed

In a perfect world we would all work on new projects, new technologies and everything would fall into place perfectly. Unfortunately this is usually never the case, at least the latter. When working with technologies that are nearing the end of their useful life or when enhancing and supporting systems that have been in operation, there can be many unknowns and consequently high levels of risk. In times of reduced budgets and heightened cost control the decision is often made to maintain existing systems, despite IT's plea to redesign and upgrade or risk system and operational failure. Assuming there isn't... Read More»

Unnecessarily Creating a Custom Business

I am often faced with the challenge of deciding what features to implement, when to implement them and even what features and requests simply are not feasible within current IT structures. In doing this I am often amazed at the abundance of assumptions that only custom software will meet satisfy the need. While all businesses are unique to some extent, the various functions and goals generally follow at least a semi-standard structure for what has to be done. We could all argue that because our businesses do things differently, we need a custom solution. In some cases I believe this... Read More»

Success Factors

There has been a lot of buzz about Outlier's: The Story of Success by Malcom Gladwell so I decided to give it a read. Basically the material is a compilation of anecdotes and short stories about success and some of the surrounding patterns. I'm not going to review the book here, but expand on the main theme of what makes someone successful. The book tells what has been engrained into many of us - hard work, perseverance, resilience and opportunity are all factors that help determine success. While it isn't always the case, generally someone that has significant experience is... Read More»

Software for All that Ails

In software development, many of us are responsible for improving the day to day operations and corresponding efficiencies of our users. We are often asked to create a system to satisfy a current or future need. While properly designed software can create much value, designing a system where there is no prototype or existing, defined process in place is highly risky. I find that for brand new systems and/or first generation automation of a system or procedure, the following should be followed: Determine Value – Review the expected return for any and all requests and make sure those involved should... Read More»