Huge Review of the DDD

Hello everyone:

Yesterday we had a meeting with our customer about the DDD or Detailed Design Document, and as predicted the complaints were important. Although the problems can be summarized in 3 points:

• The interfaces field is required
• The data field is required
• The data model must appear, becuase the implementer can not have access to the ADD.

Our opinion and reasoning behind our decision was that we have granularity zero in our components, so each component is an operation (to make life easier) and that the data and interface aspect appeared on the ADD. But as the customer is the one that commands our actions, then we must follow his premises.

So as we had 57 components, and at the same time we have to develop the SVVP or Test document and also prepare a selling; we have divide the work into two groups:

• First group: Make the changes of the DDD based on what the customer wants.
• Second group: Develop the test document.
• Already done: The presentation of the selling is already prepared and divide the presentation tasks between the members.

With this delegation of the work we are going to try to do everything the customer expects us to do; without creating a risk situation in our planning; to avoid putting a contigence plan into action.

In general we have to deliver the DDD on a saturday (we are planning finishing it tomorrow or thursday the latest) and the Test on Monday morning the latest; but we are hopefull that with our hard work, everything will have a good outcome.

Besides that, on thursday we will tell how the selling and elevator pitch went; wish us luck

Regards

Nieves

Reflection exercise about the whole project

At this point in the development of the project, we can say that we are almost finished with it, or at least, that the most complex and time consumming part is done.
That does not imply that we are going to begin being lazy about it, but now we have a clear idea of the project and the documents left are a recompilation of the work done up to this moment.

It's true that everything can fall down, but I don't think so, because if we have worked hard all these weeks(10), then we are not going to let everything go down the river in the 4 weeks left.

My general idea of the project is that we have realized that not everything is 'pink' or ideal; and that we must take responsabilities of our actions, and also if we are working in a group we have to be there for the others and left the differences apart. That does not mean that we don't have an opinion, it's more I know that I am stubborn sometimes; but when if you explain your opinions giving proofs and reasons, it's okay and an agreement is reached.

Another important aspect that this project has shown me; it's that a document TAKES HOURS and hours and hard work. And that a simple thing like a dot in a document means more that what I though it could mean.

So we will see how it goes, now that we begin the last part of the project, because we have done 75% of the project and time.

But up to this moment, I am quite content with the work done.

Nieves

3rd BPR and ADD Final Draft

Hello or goodnight readers! Yesterday we delivered the third BPR without any problems, we are going okay based on the schedule, but I am sure in the next one we are going to change it a little bit because of the selling.

Also today we delivered the last draft of the ADD, mainly is the same one as last one but adding a new operation in a component and rephrasing some parts that were left forgotten. But anyway, we will have to wait and see how it goes.

Also we are preparing now the selling an tomorrow before the meeting with the customer for the review of the DDD (we will explain tomorrow), we are going to decide who is going to do the elevator pitch and how the selling is going to be, who is going to say what, and all that jazz.

So we are in for a busy week in the project, because don't forget the SVVP or test document. Than we haven't begun yet.

So we will explain more later on.

Goodnight

Nieves