“Before you write any code, make sure you have a failing test.” This was revolutionary when first pitched in the late 90’s. Many successful entrepreneurs have practiced a similar idea: “Before you build a product/service, make sure you have paying customers.” Naresh Jain explains his approach of finding effective MVPs to validate his Educational Product and why Agile Methods simply fail to do so.
Ellen Gottesdiener and Mary Gorman have written a book titled Discover to Deliver: Agile Product Planning and Analysis. The book addresses the planning and analysis activities needed in implementing business products, with a focus on software products and business process change initiatives.
Enterprises want early and frequent customer feedback to be able to understand their needs and be able to deliver products that create value for them. Brian Murray explains how Yammer uses Minimum Viable Products to test their business customer hypotheses, and why they focus so much attention on the architecture of their products.
Eduardo Miranda from Carnegie Mellon University explains planning in agile projects, planning techniques, and the impact of agile on project management offices and the project manager role. 4
Large enterprises face challenges in innovation, budgeting, and transformation to agile. Principal analyst Michael Azoff explains Ovum’s view on creating an agile enterprise.
Suzanne and James Robertson have released the 3rd edition of their book Mastering the Requirements Process. This edition includes material focused on requirements in agile projects and outsourcing.
Laila Lotfi explains how using automated error reporting results in greater customer trust, higher renewal rates, lower maintenance costs, and fewer opportunities for the competition. 2
One of the main challenges when designing software architecture is considering quality attributes. Not only their design turns out to be difficult, but also the specification of these attributes. 2
Gojko Adzic has written Specification by Example in which he provides advice and guidelines on adopting this approach as a way to create living documentation on a software development project. 7
The Evolutionary Contract Model offers new ways to write contracts for innovative/complex product development that accommodate change and help avoid “The Curse of the Change Control Mechanism”. 4
Most software contracts are written with a waterfall approach in mind - fixing the scope, cost, and schedule. This article offers advice on how to write a contract for an Agile software project. 27
Roman Pichler discusses the product backlog along with techniques for grooming, applying, and scaling it on large projects. Chapter excerpt from Roman's book: Agile Product Management with Scrum. 6