In any project, models or mock ups are the best way for Client’s to validate and communicate with the Project Team.  Written requirements and use cases are a great start and the next best step is to be able to see the functionality.  As a Project Manager, I have seen plenty of situations where Client’s expectations were not met, and development was already completed. This often results in frustration and wasted work.

Project Methodology is defined by the Project Management Institute as “a system of practices, techniques, procedures and rules used by those who work in a discipline.”  Project methodology is full of fancy buzz words like sprints, scrum master and burndowns.  It sounds complicated, but let’s breaks down what it really means and why it’s important for an organization and their clients.

Project management is both a science and an art form. There are many project management methodologies and tools out there to help a project manager, but without the human touch, you are less likely to be successful in pushing your projects through on time, on schedule, and within budget.  A good project manager is how efficient and effective they are at getting things done. However, there are many project managers who go through the motions without the “people” aspect that really makes a project manager successful.

What value is your project manager (PM) bringing to your projects? 

One of the most contentious issues in the world of ERP and IT is how much attention to give to current state and future state ERP business processes.  Opinions on the issue run the whole spectrum on how this should be addressed; some people feel that companies should let their ERP systems dictate what new processes will be, while others feel that current state and future state processes should be documented and analyzed in detail. Many people, including myself, feel that the approach should fall somewhere in between.