Phase 1 recap

From openmichigan

Contents 1 Bugs 2 We will know when phase 1 is complete when... 3 The first phase went well because... 4 The first phase didn't come out as planned because... 5 We can improve the second phase of development by...

[edit] Bugs

[edit] We will know when phase 1 is complete when...

1. all the red functions on the Tool Functions page are GONE and the Bugs page is empty for all "Immediate" bugs.

[edit] The first phase went well because...

1. we have a functioning base for managing COs in course materials - mission accomplished.
2. the group seems to work well together to complete tasks.

[edit] The first phase didn't come out as planned because...

1. transitioning between brain waves, mock-ups, and functioning code on stable machines always takes more time than planned.
2. we had multiple communication break downs - not everyone was on the same page as to priorities, individual tasks, schedules, visioning, contingencies, and processes.
3. not enough money and expensive coffee were placed in the appropriate hands as incentives to produce.
4. //placeholder for rants about PHP, code igniter, 64bit code, MSIS, etc.//

[edit] We can improve the second phase of development by...

1. having a more structured schedule of components to be developed that include both dependencies and responsibilities.
2. maintaining a proper communication plan to inform the group of what tasks have been completed and what current issues are causing problems.
3. using a bug tracking system like trac or retrospectiva to make sure no issues get lost in the shuffle.
4. obtaining more personnel to help develop the desktop app.