 Hello, welcome to the session on agile project management in continuation with the previous contents. Let us see the learning outcome. At the end of this session, students will be able to use and adapt the iterative project management lifecycle model. An iterative PMLC model consists of a number of process groups that are repeated sequentially within an iteration with a feedback loop after each iteration is completed. Iterative approaches are used when you have an initial version of the solution, but it is known to fall short in terms of the features and functions. The iterative cycles are designed to select and integrate the missing pieces of the solutions or to add the new features. Think of the iterative PMLC model as a variant of production prototyping. The intermediate solutions are production ready, but they might not be released by the client to the end user until the final version is ready. The intermediate versions give the client something to work with as they attempt to learn and discover the additional needed features. The client would choose to release a partial solution to the end user in an attempt to get input from them. An iteration consists of a planning, launching, monitoring and controlling and closing process groups. Closing an iteration is not the same as the project. The iterative PMLC model requires a solution that identifies the requirements at the function level but might be missing some of the details at the feature level. In other words, the functions are known and will be built into the solution through a number of iterations, but the details that the features are not completely known at the beginning of the project. The iterative PMLC model embraces several types of iterations. Iteration can be on requirement, functionality, features, design, development, solutions and other components of the solution. Next we will see when to use the iterative model. The iterative PMLC model kicks in when one of the following occurs. Most but not all of the solution is clearly known. That is a few features require clarification or not understood to the user. And if you have chosen the incremental PMLC model but have a strong suspicious that there will be more than a minimum number of scope change requests, then the last one is if you have chosen the adaptive PMLC model but are concerned about lack of client involvement. So these are the cases where we use the iterative model. Next we will see the scoping phase of an iterative model. So it takes on a bit more complexity than the scoping phase of linear or incremental PMLC models. And it requires decisions that are not part of linear or incremental PMLC models. That is implementation of the intermediate solutions, that is the work products that can be problematic and final solutions that cannot be defined at the start of the project. Planning is done at two levels in an iterative PMLC model. The complete plan for building the known solution. The first iteration in this plan may be of long duration in order to accommodate building a production version of the entire known solution. If you feel that this iteration will be too long then you might consider using a tool to model the solution instead. The partial plan for the high priority functions for this approach you will begin the partial plan by prioritizing the functions and features in the initial requirements. There is a significant difference between the project team for additional project management project and project team for agile project management project. The table shows the difference. The first is the size characteristic where it could be very large. The traditional project team could be very large and in agile project management usually it is less than 15. And skill level in traditional is all levels and in agile project management is mostly the skilled people. And location is co-located or distributed in traditional project team. In agile project management it is a co-located. The experience level in traditional based project team is junior to senior but in agile project management it is skilled and senior people. In the traditional it requires a supervisor to control the team but in agile project management team unsupervised. Monitor and control phase monitor the phases and close the phases or iteration and closes the project. Let us see the characteristics. The solution is known but not to the expected depth. In simpler applications of iterative payable model features may not be clearly defined and it often uses iconic or simulated prototypes to discover the complete solution in more complex cases that requires a solution discovery, a modeling approach that could be a quick and efficient approach. Now we will see the strengths. The client reviews the current partial solution for improvement. There is no substitute to experiencing and using a partial solution for the client. This continues review by the client that tends to keep the solutions aligned with business needs and it can process the scope changes between the iterations although the simple iterative models can receive and process the scope changes request between iterations. You should try to stay in control by presenting the client with alternatives and ideas at each iteration. The projects are required to adopt the changing of business conditions. Next we will see the weaknesses. It requires a more actively involved client team than the traditional project management team. The higher the likelihood of change the more you need an active client involvement to make a good business decision regarding the change. It requires a co-located team having a co-located team is usually not possible and this places a high change project at great risk. Final solution cannot be defined at the start of the project. The final solution is a variable the less you know about the solution at the beginning the more unexpected it may be at the end. You might have started out thinking you are going to solve the entire problem but you ended up solving only a part of it because the time or budget nano or maybe the parts of the problem turn out to be the intractable and you just have to live with the best you can do. So the type of iterative PMLC models are the these are the main models prototyping and rational unified process. So we will discuss in detail about the prototyping model. The preview model that figure shows requirements are gathered from the client prototype is developed and delivered to the customer. After delivering to the customer a feedback is taken from the client and plan for the next prototype is developed. Once the iteration is completed deliver the final solution for the project. Pause the video for a while and think about what this figure represents. Yes the answer is three incremental PMLC model. So here the iterations are incremented as one two billion iterations. So answer is incremental PMLC model. Now pause the video for a while and think about what this figure represents. Yes the answer is iterative and incremental model. Iterative and incremental development is a combination of both iterative design or iterative method and incremental build model for development. During software development more than one iteration of the software development lifecycle may be in progress at the same time and this process may be described as an evolutionary process or incremental build approach. These are the references I referred. Thank you.