One of the largest areas of waste in development are poorly formed requirements. This post presents a very simple technique that can be applied to all user stories to improve quality and reduce waste, as well as examining how this can fit into your current planning and estimation workflow via the underused ‘definition of ready’. It’s a very actionable concept that you can apply immediately.
Product risk analysis (PRA) is not only useful in testing but is also applicable during the various phases of sequential or agile system development. This article introduces a different application of PRA that elevates it from project level to domain level. It shows how you can go from risk and requirement-based testing to risk and requirement-based development.
Mobile and embedded devices, more than any other technology, are an integral part of our lives and have the potential to become a part of us. This article discusses what “human experience” testing is and is not, and uses concepts from human computer interaction design theory to establish a framework for developing “human experience” test scenarios.
Chris Haddad explains in this article what Shadow IT is, what role it plays in the enterprise and why Enterprise IT needs to embrace it, adapt and address Shadow IT requirements, autonomy, and goals.
The Incremental Commitment Spiral Model: Principles and Practices for Successful Systems and Software describes a process model generator. InfoQ interviewed the authors Barry Boehm and Richard Turner.
Tracking projects is challenging when enterprises adopt agile in product development. Smaller work items and lower work in process improves risk management and supports agile execution and learning. 3
Commitment is a graphical business novel about managing project risks with “Real Options”, a way to improve decision making. InfoQ spoke with the authors about decisions, risks and technical debt. 1
Building on their work on Real Options, Chris Matts and Olav Maassen are writing a graphic novel to explain the concepts and share their knowledge. They discussed the novel and the process with InfoQ.
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor. 3
In this IEEE article, author Danny Dhillon discusses a developer-driven threat modeling approach to identify threats based on the dataflow diagrams for assessing and mitigating the security risks. 3
Risk management is a crucial discipline for projects, and finding ways to do effective risk management on agile projects will spell the difference between Agile scaling into the enterprise or failing. 5
In this IEEE article, author John Diamant talks about improving security quality of software applications using techniques like security requirements gap analysis and architectural threat analysis.