-
Notifications
You must be signed in to change notification settings - Fork 0
Iteration 1 Retrospective
yanika edited this page Mar 26, 2014
·
7 revisions
During the Retrospective Meeting held on Monday 24th March, at the end of Iteration 1, we looked back on the past two weeks and;
- Discussed our workflow
- Identified what went well
- Identified what could have been done better
- Came up with several suggestions of how to solve the identified work flaws.
We have come up with the following conclusions;
Workflow / What went well
- we had a good workflow
- We had a good work distribution
- We finished all User Stories (all points for this iteration were reached)
- The client's requests were all fulfilled
What could have been done better?
- Better point distribution of tasks during iteration planning
- We could have had better user stories (even from the client's side)
- Also if this means writing the user stories during the meeting with the client
- We could have planned a better Test Plan thus leading to more NUnit Tests.
What we'll be changing in the next iteration
- Start forming user stories during the meeting with the client and get approval
- When work is distributed, each team member works solely on his task (this is to prevent other team members from being distracted to help with another team member's problem). If a specific problem is encountered by a team member, this will be then addressed or in the following stand-up meeting or at the end of that same meeting.
- For each method we create, we will be immediately creating its test to make sure we won't end up lacking tests at the end of the iteration.