I've used this same approach repeatedly myself. It is particularly effective in turnaround situations, of which I've managed several. I have gotten into the habit of actively looking for these kinds of opportunities. I like to have a list of possible mini-projects with this kind of value, then I can "seed" my project list with these. Programmers like them because you can see the end product fairly quickly and they produce real value for the customers in ways non-techies can easily understand. And often, it's much easier to quantify the cost/benefit equation of these types of projects because of their tight scope. And because of the small size, the risk is generally small. We have to do the big projects, the transforming ones, but the 30 day blitz project is an important tactical tool to get things going and build credibility.
Rating:
I've used this same approach repeatedly myself. It is particularly effective in turnaround situations, of which I've managed several. I have gotten into the habit of actively looking for these kinds of opportunities. I like to have a list of possible mini-projects with this kind of value, then I can "seed" my project list with these. Programmers like them because you can see the end product fairly quickly and they produce real value for the customers in ways non-techies can easily understand. And often, it's much easier to quantify the cost/benefit equation of these types of projects because of their tight scope. And because of the small size, the risk is generally small. We have to do the big projects, the transforming ones, but the 30 day blitz project is an important tactical tool to get things going and build credibility.
Thomas M. MacKay