The dramatic reduction in time comes from removing the time required to move information from person to person. The key concept of a JAD session is that you get all of the major decision makers, stakeholders, and knowledge providers into one place all at the same time. JAD sessions can result in dramatic improvements-maybe 75 percent, 80 percent, 90 percent, or higher. So, this is not about reducing turnaround time by 10 percent. As an example, the time required to produce the project definition might be reduced from six weeks to one week, or perhaps even two days. How dramatic could the time savings be? Very dramatic. However, in many cases, your management and sponsor are willing to pay more for a process that takes much less time. Depending on how the JAD is implemented, it may, in fact, cost more than the traditional methods. Notice that I did not say it would dramatically reduce the cost. The purpose of the JAD session is to dramatically reduce the timeframe required to complete a deliverable where consensus is required. It appears, from your question, that you have already become familiar with the “quite a long time” process. The disagreements must be taken back to the sponsor for resolution, and perhaps another round of discussions takes place to provide further clarification and to build a consensus.ĭepending on how controversial the project is, you may get a consensus on the project definition quickly, or it may take quite a long time. Many of them read the document and say fine, but some will have questions, or they may disagree with some of the content. You create a draft project definition that is circulated back to these stakeholders. You begin to write a project definition and realize you don’t have all the information you need, so you make a second round of talking to people to ask clarifying questions. They give you enough information so that you can start to talk to other interested stakeholders. First, you might talk to your manager and the project sponsor. Let’s briefly recap how you normally define a project. In particular, based on your question, the technique can be applied to help define a project. This includes gathering business requirements, creating a project work plan, building a quality management plan, and so on. Although I don’t know the origin of the term, the JAD technique can be applied to a wide variety of areas where consensus is needed. Judging by its name, you might think that this technique only applies to developing software, but that’s not the case. The technique is called joint application development, or JAD. There is a specific technique (or set of techniques) for more rapidly gaining a consensus from a group of individuals. What can you tell me about it, and is it something that can be used on a project? I have subsequently read about a JAD technique that might help us get through this process faster. However, the time required to get everyone’s acceptance was unacceptable. The process of gaining approval obviously had value since there were some major differences of opinion on what the project was to accomplish. The last time I managed a project, it seemed like it took forever to get all of the major stakeholders to agree on what we were doing. He shares his tips on a host of project management issues in this Q&A format. TechRepublic columnist Tom Mochal receives dozens of e-mails each week from members with questions about project management problems. The benefit of using JAD is to save your team from wasting days or weeks in project definition gridlock. The JAD technique can be applied to developing software, building a quality management plan, or even defining a project. JAD sessions will speed up the project definition process
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |