The Requirements You Received Are Not Requirements

Too often when IT consultants receive software requirements for new features they are not requirements at all. At least, they are not defined as requirements. In most cases when identifying the problem the customer is likely to find a “solution” which is often what they present as requirements.

This talk shares personal experience on software development projects where badly defined requirements have had a negative impact on deadlines, budgets and most importantly customer satisfaction. It will underline what to look for when investigating functional and non-functional requirements. We will glance over the attributes that complete a requirement. We will understand how to ensure a testable requirement for successful implementation.

Video producer: https://www.boosterconf.no/

Videos

Why Learning Product Organizations Experiment Frequently

Many organizations are afraid of designing and running experiments for product development. Validation of the assumption approach has not been widely spread in the industry as a standard. Hypotheses are taken as facts and they are turned into requirements and features without verification. In contrast, other companies seem to be more customer value-oriented and validate […]

Read More
Videos

Designing a Scalable Product & Engineering Methodology

Are you bored by hearing about Spotify’s Model, Basecamp’s Shape Up, or Netflix’s “No Rules Rules”? All of them do have something in common. They tailored something unique to match both their ambition and their strengths, while honestly acknowledging their weaknesses.

Read More
Videos

Design Thinking Activities

This video explains that the six stages of the design thinking process can be supported by a very wide range of UX methods and activities. Don’t limit yourself to the most commonly mentioned methods.

Read More

Copyright © 2009-2022 Martinig & Associates