-But if we are ready to go to the market, - -2
-if we are ready to deploy our product, then we can - -3
-move to the transition phase, which has mainly to do - -4
-with deployment and maintainence of a system. So what are the - -5
-main activities in the transition phase? As we discussed in - -6
-our initial lessons, in most real world cases, there are issues - -7
-that manifest themselves after deployment, when we release our software and - -8
-actual users interact with the - -9
-software. Specifically, users might report failures - -10
-that they experienced while using the system. So, what we call - -11
-bug reports. Or they might report improvements they might want to see - -12
-in the software. So typically these will be new feature requests. And - -13
-in addition, there might be issues that don't come necessarily from the - -14
-users but that are related to the fact that our system - -15
-has to operate, has to work in a new execution environment. For - -16
-example, the new version of an operating system, or the new version - -17
-of a set of libraries. When this happens, we have to address - -18
-these issues by performing maintenance. Specifically, corrective maintenance - -19
-for bug reports, perfective maintenance, for feature requests, and - -20
-adaptive maintenance, for environment changes. And the result of - -21
-this is that we will have a new release - -22
-of the software. Other activities that are performed in - -23
-this phase include training, customer service, and providing help-line - -24
-assistance. Finally, if you remember what we saw when - -25
-we were looking at the banking IT system example, - -26
-the cycles within a development are not necessarily completely dis-joined, but - -27
-they might overlap a little bit. So something else that might - -28
-happen in the transition phase is that a new cycle may - -29
-start. So there might be some activities that are related to - -30
-the fact that we're starting to think about the new cycle. - -31
-So now let's see what kind of outcome these activities will - -32
-produce. The first one is a complete project with all the - -33
-artifacts that we mentioned before. Another outcome is that the product will - -34
-be actually in use. So the product will be in the - -35
-hands of the users and the users will start using it, will - -36
-start interacting with it, for real, not just in a beta testing - -37
-setting. Another outcome will be a lesson learnt. What worked. What didn't - -38
-work. What should we do different in the next cycle or in - -39
-the next development? And this is a very important part of the - -40
-whole process, because it;s what provides - -41
-feedback between cycles, and between projects. - -42
-And as we said before, in case we have a next released - -43
-planned or a next cycle coming up, we might want to - -44
-start planning for the next release. So another outcome will be - -45
-the plan for the next release. So similar to the other - -46
-phases, also for the transition phase, we have a milestone, which - -47
-is the fourth milestone in this case. And therefore we - -48
-have evaluation criteria for the transition phase that will define whether - -49
-we've reached the milestone or not. And in this case, one - -50
-important assessment is whether the user is satisfied. So users are - -51
-actually using our product now, so we can get feedback - -52
-from them, we can see whether the product makes them - -53
-happy or not. And we continue assessing whether our expenditures - -54
-are fine with respect to our estimates. And in this case, - -55
-problems with this milestone might lead to further maintenance of - -56
-the system. So for example, we might need to produce - -57
-a new release to address some of the issues that - -58
-the users identified, as we discussed a couple of minutes ago. -- cgit 1.4.1