Process Improvement

Please login or join to subscribe to this thread

What term do you use for low effort implementations?
Network:0


We have defined our desired process to identify, qualify, and manage Projects. One of the criteria we use to identify a 'project' is an expected effort of 4 weeks or more.

We now want to create a much lighter weight process for implementations that take less than 4 weeks. We want to track these as something other than 'Small Projects'. A search shows that many use the term Enhancement, but that conflicts with our definitions of Feature and Enhancement requests.

I am interested in learning how most orgs label these low effort implementations.

Thanks
Sort By:
Network:17



In the State of Florida, many of those projects are considered O&M. In other places I've worked, there has been a 250 hour LOE threshold. These smaller projects were not subject to the same level of governance as larger projects.

More on O&M -

1. Operations and Maintenance (O&M) activities that support an existing product or service to keep it in conformance with its originally intended specifications, functionality, and service levels are exempt from these standards. O& M activities include:
a. Adaptive Maintenance ? the modification of a product, performed after delivery, to keep a product usable in a changed or changing environment.
b. Corrective Maintenance ? the reactive modification of a product performed after delivery to correct discovered problems.
c. Perfective Maintenance ? the modification of a product after delivery to detect and correct latent faults in the product before they are manifested as failures.
d. Preventive Maintenance ? the modification of a product after delivery to detect and correct latent faults in the product before they become operational faults.
Network:0


Thanks for your response, Ellik. I should've clarified in my OP that my question is specific to new Feature or Enhancement requests, not Maintenance work.
Your info on classifying Maintenance projects is timely and useful as we will be looking at those next, thanks!
...
1 reply by Ellik Hawkins
Jun 14, 2019 10:13 AM
Ellik Hawkins
...
My pleasure. I agree that O&M may not fit is some instances. Many orgs that I work with use the portion "support an existing product or service to keep it in conformance with its originally intended specifications" to justify including minor mods or enhancements. In my industry, many enhancements are based on statute or legislative mandate, so folks use O&M as a catch-all for smaller projects, since O&M are not subject to the same governance and compliance in Florida state gov't.
Network:17



Jun 14, 2019 9:59 AM
Replying to Naren Durgampudi
...
Thanks for your response, Ellik. I should've clarified in my OP that my question is specific to new Feature or Enhancement requests, not Maintenance work.
Your info on classifying Maintenance projects is timely and useful as we will be looking at those next, thanks!
My pleasure. I agree that O&M may not fit is some instances. Many orgs that I work with use the portion "support an existing product or service to keep it in conformance with its originally intended specifications" to justify including minor mods or enhancements. In my industry, many enhancements are based on statute or legislative mandate, so folks use O&M as a catch-all for smaller projects, since O&M are not subject to the same governance and compliance in Florida state gov't.
Network:303



We just use a numerical coding system with 1 being a very large change that everyone starts to pay a lot of attention to, down to 4 which is a pure copy of a previous project. It's essentially high, medium, low, and no change. It's office jargon, but once everyone knows what the thresholds are, when I say Code 2 in the office, everyone knows what I mean.

We have a couple other simple classifications for other types of change as well (e.g. Major vs. Minor), but the important thing is that you have criteria for the change, and you know what they mean, not that everyone in the industry does.
Network:17



I think the term O&M could be used in any industry. I am in State Government, Software Development Project Management specifically.
Network:230



That's like happen to me right now Naren. The commercial side, they don't want provide item excluded on budget plan. But on another side, operation don't want accept if the item not compatible with our standard specification. So they've different orientations & concern. Because this is about budget I think it is not my capacity to determine which best solution to solve this case. I decided to consult with our deputy CTO and he still wants the item have to use consider with our standard specification to ensure our services can deliver as well. It's not only about prestigious, more than that. We'll try to keep the reputation of our brand and we don't want to lose the trust of our customers. Finally he wants for the next project plan, supposed to be we create multiple options classification like Keith said start from low, medium and high including risk possibility (strength and weaknesses). Then let him choice which the option fit in with him consideration.

Please login or join to reply

Content ID:
ADVERTISEMENTS

If you can't convince them, confuse them.

- Harry Truman

ADVERTISEMENT

Sponsors