Articles & Posts

Articles and Posts 4 mins 644 Views 0 Comments 0 Likes

Are requirements gathering practices a thing of the past?  How can teams deliver software that meet the expectations of the customer without clearly documenting requirements?

In this article,  Meredith Aourtemanche, executive aeditor at Tech Target, argues that a focus on hands-on, experimental, prototype-driven appoach to software design might be a better approach.

A streamlined, here-try-this approach bypasses the typical -- and laborious -- process of handing requirements among UX researchers, project managers, developers and testers. And even when that traditional process flawlessly captures requirements, customers aren't easy to please. There's often a disconnect between what they intuitively know an application must do and how they articulate demands to the development team.

A User Experience (aka UX) driven approach is at the core of Design Thinking enabling analysts, developers, testers to to take a "no-requirements" approach to software prototyping, buckling the status quo of most organizations.

According to Gartner, design thinking is based on six key practices or mindsets:

  • Empathy
  • Show, Don't Tell
  • Experiment
  • Be Mindful  of Process
  • Action-Oriented
  • Collaboration

What do you think?  Is prototyping replacing the need to gather and document requirements?

Continue reading at TechTarget

Login or Register to download
2020-06-28 Software Prototyping instead of Requirements Gathering? Software Prototyping instead of Requirements Gathering?

Comments / Discussions

Please login or register to post comments.



Free Newsletter

Requirements.com is trusted by leaders and experienced professionals across the world. Start your subscription today, for free.