Closed bajabob closed 8 years ago
bajabob
commented
8 years ago @mdyl we will probably want #42 and #41 printed individually on that small poster size before it is due on Tuesday. I advise that once the tasks are completed by @wvance (by your standards), that you ask Cassandra to verify before printing.
bajabob
commented
8 years ago @mdyl This is a reminder to followup with Cassandra regarding our requirements document you handed her on Tuesday.
Additionally I would like to report that @wvance has begun working with a tool to generate our Gantt and CPM models. He mentioned that he is just going to complete them and there is no need for @JenningsF to help. This leaves Jennings with little assigned tasks this sprint. I know he is busy with his speech and leadership assignments, I advise that if you need to hand off duties like printing or other small tasks that you consult him for aid.
bajabob
commented
8 years ago @mdyl reminder to followup with Cassandra on Thursday to clarify:
As the team lead, I am to take all completed issues and certify that they have been completed to team standards. I am to drive any issues that have yet to be completed and follow up with team members if something needs changed or updated. As such I am to gain a general or full understanding of each completed task so that I can properly present said information at my weekly team lead meeting.
Itemized Objectives for Team Lead
No Close Policy
The team lead (Matt Dyl) of the project solely has the power to close any issues for a given sprint. No team member shall close a task unless otherwise delegated by the team lead. When a team member feels that a task is completed, they are to 'tag' Matt in the issue, state that the issue has been resolved and Matt will follow up with issue owner if any changes need to be made.
Issue Completion Flow Exceptions
The only exceptions to the No Close Policy are listed below.