I know that roject management is usually associated with projects that have a duration longer than a couple of days to a week. However, in my current position I am finding it difficult to sperate the project management skills I have learned from the need for a fast paced software "bug fix" environment.
The environment that I work in allows 20 - 40 small projects to be completed a week. Each of the projects are unique in nature, not just elements of a larger project. When the call comes in, a work order is created, and a developer is assigned to handle the task.
What I am trying to do is formulate a strategy for managing these tasks in a more structured way. The current management is used to just handing off the tasks and they get done when they get done. There is no start/end relationship for tasks as they come in, only a priority system that says when a project must rise to the top. Everything that isn't top priority is really up to the developers discretion as far as schedule goes.
Are there any good methodologies that someone can point me to that would increase productivity, refine scheduling practices, or generally make this chaotic environment more structured?
Regards,
Dan Bish Saving Changes...
Sort By:
Mark Price PerryBusiness Driven PMO Evangelist| BOT InternationalOrlando, Fl, United States
Hi Dan, regarding a strategy to handle change management tasks in a more structured way... one approach is to define and use your change management process in much the same way that you would any other PM or SDLC process. This doesn't have to be complicated. Change management steps like Request, Plan, Develop, Test, Approve, Release can be setup in the context of the tools that you are already using. Many of the vendor change management tools have the process somewhat imbedded as well. The tools, however, may not have the organization unique criteria that can help you optimize your process. For example, any change request that is more than 2 weeks or that involves foreign language support, we treat as an SDLC project effort. This may not be the "right" way, but it is "our" way, for now. You may have similar organization uinique criteria that help you optimize the results your change management team. Are you happy with your tooling..? As 20 to 40 change request projects per week can be a challenge to manage, you may find that some of the vendor products out there can help you. Many of these tools can be setup in a day, offer lasting quality, and are very attractively priced; unlimited users for $1,000. Check out Jira by Atlassian. Hope this helps. -- Mark Perry, VP of Customer Care, BOT International Saving Changes...
Hi Dan for what it is worth I look at what tools are on offer and convert them into the way the organzation works.
Based on prior knowldge Firstly I create a paper gnatt chart which is 2 months in advance broken down into 8 weekly work schedules which then gets converted into project 200 within this schedule there are spaces this allows me then to fit in other works which come in on a daily basis
But at the end of the day it is me who sets the Priorities and not the techies
this in turn allows me to plan effectively, keep control and manage the projects in a timely fashion
