|
|
Optimize with a SATA RAID Storage Solution
Range of capacities as low as $1250 per TB. Ideal if you currently rely on servers/disks/JBODs
Page 2 of 3
In CRP, you lock your savviest business managers and users in a conference room (hence the name) with one or two of your gurus, a plain-vanilla or current-state version of the system to be implemented or enhanced, a big stack of test cases, and pizza.
The business managers and users run the test cases through the system, documenting the business process they use as they do so. Along the way they point out, "If you could get the system to do x, we could handle this case more effectively," at which point the guru either gets the system to do x, or proposes an alternative that would be much easier to implement while still supporting enhanced business effectiveness.
The system is done when the business managers and users figure they've reached the point of diminishing returns -- or when nobody can stand the thought of another bite of pizza.
App dev acceleration technique No. 3: Humanity-based case handling
Michael Hugos described this technique in his excellent "Business Agility" (2009), although that wasn't what he called it. The concept is simple: When implementing any system, 20 percent of the cases
handle 80 percent of the transactions, more or less, but every case takes about the same effort to implement.
The application team should deliver a system that handles the right 20 percent of the cases, (this is essential) knows how to kick out the rest for human beings to deal with, and allows those human beings to input the results back into the system when they're done -- that is, humanity-based case handling. If the system is programmed this way, IT ought to be able to deliver the system five times faster than if it had tried to deliver a complete system in the first release.
Two releases later, each taking care of the remaining 20 percent of the cases that handle the remaining 80 percent of the transactions, and the system will handle more than 99 percent of the situations that come up. The business should be able to handle the rest through humanity-based case handling without breaking a sweat.
App dev acceleration technique No. 4: Integration-free implementation
A fact IT professionals know but very few people bother to mention is that integration is where most IT complexity lives.
Most SaaS implementations aren't integrated into the rest of a company's applications portfolio -- and when it comes to shadow SaaS implementations, none of them are. This is the single biggest reason SaaS implementations have a reputation for being quick and easy.
As it turns out, given a choice between speed and integration, many business managers are quite content to live with manual rekeying -- so offer them the same alternative when IT is involved. They won't take you up on it, but that's OK. At least you'll have offered an in-house implementation that's just as quick and easy, and they'll know where all of the extra time and effort goes.
App dev acceleration technique No. 5: Only launch fully staffed projects
Here's something you can use from Goldratt's critical chain methodology, even if you don't use anything else from it. Goldratt
defined "fully staffed" to mean that a project never waits for a team member to become available.