Best Practices for Software Projects: JAD Sessions

Member Submitted

Most of us have worked on projects that were not well organized and the requirements gathering process dragged on for months, commonly referred to as "analysis paralysis". Joint Application Development (JAD) sessions are a set of intense meetings held off-site where executives, developers, and end-users define the exact requirements needed by a software solution. By holding JAD sessions, your team can more quickly define requirements, get executive buy-in, eliminate irrelevant requirements, and reduce political jockeying between team members.

About the author

Steve Miller's picture Steve Miller

Steve Miller is the Vice President of ALM Solutions for AutomatedQA. With over 25 years of experience, Steve has extensive knowledge in project management, software architecture and test design. Steve publishes a monthly newsletter for companies that design and develop software. Be sure to check out our other newsletters.

AgileConnection is one of the growing communities of the TechWell network.

Featuring fresh, insightful stories, is the place to go for what is happening in software development and delivery.  Join the conversation now!