The Commitment (Monday Lunch)

The Commitment (Monday Lunch )

To make a long story short, Gary likes it. He pays for lunch. I've brought my five sheets of paper (and my pocket agenda), and we scribble while waiting for the main course.

The bad news is that I did not completely understand the requirements. Gary wants all of his developers to accumulate data in a single database, over their local area network; he doesn't want to have each of them accumulate data in his or her own database because it's not that easy to merge the data. Also, they don't always work from the same machine, especially when they do testing. We make a few other touch-ups and clarifications to the requirements, but that network feature has me worried. It has consequences for my architecture and requires much more setting up and testing. Plus, we have identified the need for an administrator to maintain the database.

So, more or less on the fly, I adjust the documents that I prepared this morning.

The Vision, Take Two

I fix the Vision, adding that network feature. I also add a couple of ideas for future development that we discussed when I touched on the idea of making a business of this. Although I won't implement them in this round, they might constrain some design choices.

The Plan, Take Two

I decide not to take too many chances . To mitigate the big architectural risk, I shift the LCA Milestone (end of Elaboration) to dinner on Tuesday. I plan to do Construction over two days, with two iterations. For the first iteration, on Wednesday, I'll test and make sure the "single-person" version works fine, and on Thursday I'll develop the client/server feature over the network and test that. This will shift Transition to Friday for a final product delivery Friday evening. Gary also wants me to come to his office Friday morning to install the beta version and try it in situ.

Figure 4.5. Modified Plan.

graphics/04fig05.gif

The Risk List, Take Two

Now there are five new risks to add:

Figure 4.6. Assessing Risks, Take Two.

graphics/04fig06.gif

My biggest risk? If things go wrong, I'm jeopardizing the hiking trip I've planned for this weekend .

The Business Case, Take Two

Now we're talking about a full week of work, so I raise my estimate. Gary will have a return on his investment in only eight-and-a-half months, but he thinks a reasonable commitment is to pay me two-fifths of the project fee if I get to the LCA Milestone by Tuesday night. He promises to send me a purchase order for the Elaboration phase as soon as he is back in his office.



The Rational Unified Process Made Easy(c) A Practitioner's Guide to Rational Unified Process
Programming Microsoft Visual C++
ISBN: N/A
EAN: 2147483647
Year: 2005
Pages: 173

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net