Best Practices for PM Methodology in a Production Shop?
Dan GrimmProgram Manager| CareFirst BlueCross BlueShieldBaltimore, Md, United States
I work in a data processing unit for a health insurance company. But, more specifically, I work on the support team for the data processing group. The support team is made up of a manager, a team of a half-dozen business analysts, led by a senior business analyst, and two project manager. The BAs are responsible for maintaining various aspects of the production work (department communication, file processing, etc), as well as providing support on special initiatives. The implementation of the special initiatives are led by one of the two project managers (of which I am one).
I've been in discussions with my manager about how we can streamline work that is being done. One area we are looking at is how can we better utilize Project Management best practices in managing the work that is being done by the business analysts. While much of the work they do is routine, and therefore outside of the strict definition of a project, there are enough changes on a daily basis, and new tasks, that some features of project management would still apply.
If someone were to ask you what is the most valuable best practices from Project Management methodology (PMBOK, PRINCE II, etc), what would it be? Would it be the emphasis on planning? The change management? The need to include Monitoring and Controlling in every project? The mandate to celebrate every project at it's completion with a party?
Let me know what your best practices for applying PM methodology to a production shop are. I'll post the best responses to my blog. Thanks.
Dan G.
www.danspmblog.com Saving Changes...
Sort By:
Jeff DahlProject Leader| Edward JonesMaryland Heights, Mo, United States
The one tool that I have found to be the best tool I have used to date is the Input/Tool & Technique/Output tool from the PMBOK.
I have used this in almost every work flow discussion that my projects impact plus it is a simple tool to train the end users on.
This tool allows the users to continually review each work flow they are involved in to see where something new fits in, as well as what it impacts if implemented.
This has also helped us in resource planning when the users review which tools, which include software, servers, web applications, mainframe cycles, etc., and has led to the launch of new projects to support the new work flow.
Senior Advisor to the CEO| PMISterling, Va, United States
Hi Dan - also take a look at ProjectHEADWAY here on gantthead. The process, particularly at its lowest level, contains a lot of detail. Saving Changes...
Elizabeth HarrinDirector| RebelsGuideToPM.comLondon, England, United Kingdom
At a really simple level it sounds as if you could do with some process diagrams and checklists. They are business analysts, I'm sure they can come up with something. Do your BAs also fulfil the BA role of eliciting requirements, and linking the process and technical requirements back to the end goal? If so, then I would ask them to be involved in how you go about standardising and streamlining the work. If not, ask them anyway as it will also affect them.
I don't think it matters which project management methodology you use, provided you only take from it the bits that are relevant to the challenges you face. Saving Changes...
Gary HarveyVP Technical Services| PinnacleVienna, Va, United States
Dan - as you say it doesn't really sound like an environment where project management would be the primary management approach. I've managed Support teams before and the management systems we used involved the following:
- make sure you have a good understanding of the different types of work that the team performs
- standardize/template the working practices
- get good visibility through timesheets of where people's time is spent
- manage the incoming workload, assigning it to teams and keeping track of escalations etc. through somelike a helpdesk system
Focus on the front-line people and keeping the management systems 'light' as nobody in those environments has a lot of time for preparing plans etc. Saving Changes...
PMI Team Member
