How to Prevent Software Re-design

The problems most companies have with software development are due to poor requirements rather than coding.  Developers know how to code but the business requirements are most often incomplete and don’t effectively communicate the business needs.  The lack of effective requirements gathering and writing leads to 82% of the software re-design and maintenance efforts causing companies to waste millions of dollars a year on ineffective software implementations and lost product to market opportunities.  These statistics are based on studies done by James Martin a leading methodologist.

An important aspect of the iterative development approach is the Joint Application Development (JAD) process.  JAD is used as a technique for developing business system requirements.  The purpose of JAD is to bring together IT and the business community in a structured workshop setting to extract consensus based system requirements.  This is accomplished by using a trained JAD facilitator and customized, planned agendas to assist the participants in arriving at complete, high quality requirements.  Experience has shown that the JAD process substantially reduces development time, costs and errors. 

JAD is typically used in the early stages of a project life cycle. Pierson Requirements Group, Inc provides training and mentoring and shows how a project can be supported through Joint Application Development workshops.

Agile/Iterative development methodology includes JAD techniques for determining user requirements. These requirements are reflected in a set of products that are produced using Object Oriented Analysis and Design.  Pierson provides training for Agile Requirements Gathering & Iteration Planning and JAD Facilitation & Requirements Gathering Training Seminar using Use Cases.  Both these classes provide techniques that can be used by your project teams to achieve consensus-based requirements.

About Joy Matthews

Joy E. Matthews is the cofounder and Vice President of Training and Consulting Services for Pierson Requirements Group, Inc., (www.piersonrequirementsgroup.com), founded in 1990. She is an Information Systems Specialist with expertise in implementing Iterative Development and Joint Application Development using many development tools. She is accomplished in business modeling and facilitation techniques. She has participated in all phases of Information Engineering systems development and Total Quality Management projects. She has successfully completed Business Process Re-engineering, Information Strategy Planning, Business Area Analysis, Functional Area Analysis and Business System Design projects for a number of organizations and is a certified facilitator. Joy trains the latest in UML and the use case methodology using JAD. She is an expert in JAD and UML best practices and industry standards. She is the co-author of Pierson’s repeatable development Methodology for Multi-Tier Architecture projects using Object-Oriented methods and JAD. Joy is the author of the JAD Facilitation and Requirements Gathering Seminar: A Process for Implementing Object-Oriented Projects. She is accomplished in Object-Oriented Requirements Analysis, Analysis and Detailed Design. She has facilitated and managed projects for all phases of the system development life cycle. Joy is the author of the following seminars: Requirements Gathering & Writing Seminar using Data Techniques, JAD, UML and Use Cases, Business Analysis Seminar, Requirements Gathering & Writing Seminar using JAD, Use Cases and UML, User Acceptance Testing Seminar, Requirements & Specifications Seminar, Facilitated Session Leader Seminar, Learning Use Cases and UML Seminar and Writing Requirements That Work Seminar. Joy can be reached at jmatthews@piersonrequirementsgroup.com
This entry was posted in Business Analyst, Requirements & Testing and tagged , . Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>