1 / 11

Manvika Singh (03170102709) Amandeep Kaur (05670102709)

JOINT APPLICATION Development(JAD ) JAD was developed by Chuck Morris and Tony Crawford of IBM in 1970. Manvika Singh (03170102709) Amandeep Kaur (05670102709). What?. Joint Application Development, or JAD, is a process originally developed for designing a computer-based system .

dustin-hardy
Download Presentation

Manvika Singh (03170102709) Amandeep Kaur (05670102709)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. JOINT APPLICATION Development(JAD)JAD was developed by Chuck Morris and Tony Crawford of IBM in 1970 Manvika Singh (03170102709) AmandeepKaur (05670102709)

  2. What? • Joint Application Development, or JAD, is a process originally developed for designing a computer-based system. • JAD is a technique that allows the developers, managers, IT Professionals and end users to work together to build a product. • It is a series of highly structured interviewed sessions and is aimed to achieve project’s goal.

  3. JAD Scope • The JAD should cover the complete development life cycle of a system. • The JAD is usually a 3 to 6 month well-defined project. • For large-scale projects, it is recommended that the project be approached incrementally, and that separate JAD's be used for each increment.

  4. Why? • JAD reduces the amount of time required to develop systems since it eliminates process delays and misunderstandings and improves system quality. • It also improves the quality of the final product by focusing on the up-front portion of the development lifecycle, thus reducing the likelihood of errors.

  5. How? • JAD centers around a structured workshop session. • Participants get together in a room to discuss the problem/project. • Everyone hears what the rest of the group has to say.

  6. JAD Structure • They are less frequent • More structured, and productive • An agenda provides the structure • The facilitator directs the process • Visual aids clarify concepts being discussed and the group dynamics, with constant feedback, stimulates creativity

  7. . JAD participants • Project sponsor • Project lead • Facilitator • Scribe • End users • Developers • Observers • Subject matter experts

  8. JAD Process Steps  • 1. Define Session: Define the purpose, scope, and objectives of the JAD session, selecting the JAD team.2. Research Product: Become more familiar with the product or service, gather preliminary information, obtaining any models. • 3. Prepare: Prepare any visual aids, developing a realistic agenda, training the recorder, and preparing the meeting room. • 4. Conduct Session: Follow agenda to gather and document the project needs and requirements.  • 5. Draft the Documents: Prepare the formal documents. 

  9. Pitfalls • Sponsor not really committed - no resources • Unclear goals or objectives - lack of direction • Too many or too few members • Not enough communication with outsiders affected by decisions • Timelines aren't kept • Meetings aren't well facilitated • 1 or 2 members dominate discussions

  10. BENEFITS OF JAD • Enhanced communication and relationship between business end users and IT personnel • Build consensus and ownership • Reduced system cost and development time • Reduced function creep • Improved system quality and productivity • Design cross-functional solutions • Helps project teams get focused and stay focused • Helps you get the right job done at the right time!

  11. Thank you

More Related