home

System Transformation: Be Careful or You Will Not Get What You Asked For

by Larry Goldberg and David Pedersen

Companies will sooner or later have to re-invent their legacy systems, add improvements to them, or significantly change their capabilities.  This may be driven by business re-engineering, process improvement efforts or replacing an out of date system that can no longer be supported.  All of us who have been involved in these projects know that these are amongst the riskiest of projects. We set out some ideas to mitigate that risk, and potentially save money.

AttachmentSize
SystemTransformation_BeCarefulOrYouWillNotGetWhatYouAskedFor.pdf258.08 KB

    Sponsored Announcements & Special Offers

view counter

Whitepaper from HP - Why Focus on Requirements Definition Management in the Application Lifecycle?

Increasingly, smart businesses are looking much closer at requirements definition (RD) and requirements management (RM) (sometimes grouped together under the Gartner-coined phrase, requirements definition management (RDM)) to streamline the entire application lifecycle. Why? Because systematic and effective RDM captures software defects earlier in the lifecycle, and it reduces the overall likelihood that defects will be introduced. That’s important. How important? According to one study, the cost to fix a defect after delivery is more than 100 times the cost to fix it in the requirement and design phase. No business wants to be hit with that bill. Now to add to this the growing interest in agile development techniques as a way to deliver higher quality applications and we have an interesting recipe for success.

Download a Free Copy

view counter
© 2007-2010 Requirements Networking Group All rights reserved. contact | advertise | privacy
Requirements Networking Group