A big risk in software development is “knowledge risk.” This is the risk that someone is the only person who knows how a particular part of the system works. The project could be in serious trouble should the person leave the company or generally become unavailable. We have a term for this ...

Related Post

• Distributed R&D: Beyond just Cost Benefits (Aspire Panel Discussion)
• “Building Software Solutions using Web 2.0 Technologies” – Webinar
• Product Development and Customer Development
• Agile Development Tools, Myths and Best Practices – Interview with Siddharta Govindaraj
• Software usability: Common myths

Software product companies who say, “We are an entrepreneurial company. We cannot be afraid of risk” may have to rethink that statement. This is due to the fact that every software development project comes with a sizeable amount of risk and this risk has to be minimized to the level where ...

Related Post

• Using The “Truck Factor” To Manage Knowledge Risk
• A Great Product Vs. Good Enough Software: The Quality Perspective

During the Producteering Breakfast series held at the SD Forum in California last month, the majority of participants (from the ISV community) held the view that a flawless and high quality product need not be the goal when attempting to build a successful product. Instead, a product that fulfilled ...

Related Post

• The Making of Great Products: The value of prototyping
• Aspire Systems among the TOP IT Innovators
• Using The “Truck Factor” To Manage Knowledge Risk
• Performance Engineering – Best Practices
• Risk management in Software Product Development