Vision and Scope document done... sort of.
Okey, so I didn't have the time to check out reflector or CodeMetrics today. I'll probably have to do it after the weekend instead. I did at least manage to read some more in Pfleeger & Fenton. Furthermore I've studied the MSF process a bit closer, and printed down a draft of the vision and scope document. I tried to recollect the things I've been discussing with Magnus about for a couple of days ago regarding our project. Now, at the time of writing, he is reviewing the document. Hopefully we will get it done tonight so we can send it to Nils for some feedback.
One thing I've noticed is that it's kinda hard to know what parts of the document templates for the MSF process model you could exclude from our project. Not all headlines are applicable, since we are doing our master thesis and the project team just consists of two people - we're not doing a traditional software engineering project with a full team. We are supposed to adjust the model after our prerequisites, and thus we've tried as much as we could. The feedback we will get when we send the draft to Nils will probably guide us well.
Two more deliverables left to produce in this phase (Envisioning phase):
It would help us a lot to have our initial meeting with Dag soon. It feels like it's hard to delimit our project without the guidelines he is going to give us, which in turn makes it hard to produce any real value in the deliverables for the project phase. I do know that they are putting in a lot of effort to make the meeting happen as soon as possible, so I'll just keep my thumbs crossed and hope for the best.
Oh, and yes - we got some tips from Dag about what books that should suit us well. He has a list with books here, and we will get the opportunity to look at them when we meet. So I'll wait until then before I dig deeper into books about VSTS/TFS
Things to do:
One thing I've noticed is that it's kinda hard to know what parts of the document templates for the MSF process model you could exclude from our project. Not all headlines are applicable, since we are doing our master thesis and the project team just consists of two people - we're not doing a traditional software engineering project with a full team. We are supposed to adjust the model after our prerequisites, and thus we've tried as much as we could. The feedback we will get when we send the draft to Nils will probably guide us well.
Two more deliverables left to produce in this phase (Envisioning phase):
- Project structure
- Risk assessment
It would help us a lot to have our initial meeting with Dag soon. It feels like it's hard to delimit our project without the guidelines he is going to give us, which in turn makes it hard to produce any real value in the deliverables for the project phase. I do know that they are putting in a lot of effort to make the meeting happen as soon as possible, so I'll just keep my thumbs crossed and hope for the best.
Oh, and yes - we got some tips from Dag about what books that should suit us well. He has a list with books here, and we will get the opportunity to look at them when we meet. So I'll wait until then before I dig deeper into books about VSTS/TFS
Things to do:
- Send the Vision and Scope document to Nils after Magnus' review
- Write the Project structure document
- Finish the project plan in MS Project
- Write the Risk assessment document
- Check out Reflector and code metrics
- Read more about Software Metrics
- Find more reading material about Software Metrics
- Probably some more stuff I can't remember right now.
