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

Collaborating With Stakeholders

To make UX research and requirements gathering more efficient and effective, you have to get everyone in the software development team and the user representatives involved. When the teams understand user concerns and usability issues, they become better at preventing problems.

Read More
Videos

Product Managers Best Practices to Build Highly Effective Teams

This talk shares product management best practices and experiences with you in hopes they will help you in your product development journey to build highly effective teams. It covers key topics including (a) working together, (b) managing and prioritizing the work, (c) customer discovery and readying stories, (d) measuring what and how we work, and […]

Read More
Videos

Mapping Customer Experiences: From Insight to Action

Visualizations are a key tool that help organizations change their perspective. Though no silver bullet, mapping experiences diagrams seek to align customers’ experiences with how businesses operate. You are surely familiarly with things like customer journey maps, service blueprint, experience maps, and more.

Read More

Copyright © 2009-2021 Martinig & Associates