![]() Another issue with long modeling sessions is that fatigue begins to set in among participants, modeling can be a mentally draining activity, reducing the quality of their work. AM’s principle of Rapid Feedback implores that you to reduce the time between modeling something and verifying your model, either by reviewing it with someone else or by following the practice Prove It With Code. My experience is that modeling sessions of greater length than two or three days puts your effort at risk – the longer you go without feedback the greater the chance that what you are modeling does not reflect what actually needs to occur in the case of requirements or what will actually work in practice in the case of architecture. To reach these goals you often find that you need to hold initial modeling sessions that may take several hours or even several days because you have a lot of ground to cover at the start. During this phase of your initiative which there is a great need to define the scope and to set the initial requirements, as well as to envision a candidate architecture based on those requirements. ![]() You are likely to hold longer, initial modeling sessions at the beginning of the lifecycle. This change in focus will motivate different styles of modeling sessions, including different durations, throughout your effort. It is important to understand that your focus changes throughout the lifecycle, at the beginning of the lifecycle you are typically more concerned with understanding “the big picture”, in the middle of your lifecycle you are more concerned with building specific parts of your system, and at the end of the lifecycle your focus is on transitioning your system into production. Why such a wide range? To answer this question you need to first consider when modeling sessions occur – modeling occurs throughout your entire development efforts. The duration of effective modeling sessions often range from several minutes to several days, with the majority of sessions lasting between ten and thirty minutes. ![]() How Formal Should a Modeling Session Be?.My experience is that to make modeling sessions effective you need to rethink your approach to them, focusing on what works and excluding what doesn’t.Let’s consider the following issues: Traditionally the effectiveness of modeling sessions seems to range widely, from being very productive to virtually useless. Modeling sessions are an important part of any software development effort because they provide an opportunity for people to collaborate together in order to communicate their needs, to come to a better understanding, and ideally to work towards a solution. Rethinking Modeling Sessions: Applying Agile Ways of Thinking (WoT) A modeling session is an activity where one or more people focus on the development of one or more models. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |