Practice II: To-Do list

Keep a to-do list for short term and long term tasks, so we never "forget" them.

• To-Do Lists are prioritized lists of all the tasks that you need to carry out.
• They list everything that you have to do, with the most important and the least important tasks.
• By keeping a To-Do List, you make sure that you capture all of the tasks you have to complete in one place
• To-Do Lists are very simple, they are also extremely powerful, both as a method of organizing yourself and as a way of reducing stress. And most important thing, you do not have to remember, you delegate that to a system called "To-Do list".

Practice III: Check point meeting

• This meeting should be conducted at around 3 pm to review the targets decided during the GM meeting
• Purpose of this meeting is to
    ♦   Remind the targets for the day,
    ♦   Evaluate progress and address obstacles,
    ♦   Trigger communication in case of ambiguities
    ♦   Identify risk to the schedule
    ♦   Communicate dependencies
• At the end of the meeting, everyone should have a sense for their own progress, team progress and should trigger required communication

Practice IV: Daily status

Communicate daily status via email and through task tracking tool. This helps to keep track of the project and task progress. Also, this is a self management tool to monitor daily objectives.
Generally, project leader reconciles the status for the project.

Practice V: Weekly health check

• Meeting conducted on each Friday
• Review the progress, consistency of process and reconcile project reporting
• Identify achievements of the team members
• Retrospect and identify process improvements

Practice VI: Communication

• No communication is over communication. Keep the communication proactive, effective and continuous.
• Avoid assumptions and if any, communicate those.
• Do not wait for end of the day or a meeting to communicate things that impact the project, deliverables and stakeholders

Practice VII: Code management

1. Update your local code every morning from SVN
2. Check in code for every task. Please do not check in the code at the end of the day.
   Before check in, take a diff from the repository. Make sure each file has diffs specific to changes you made. There shouldn't be any white space difference(s) between local and remote file.
3. Update/Merge the code if the file was modified before your check in. If there was a merge, test the functionality again.
4. Check in the code with proper comments/issue#. If you have to fix issue# 2, issue# 6 and issue# 7, please have 3 sets of checkins corresponding to the issue fixes
5. If your check in needs some environment updates/changes, mail about those specifically to the affected parties
6. The code in repository should always compile and work.
7. Never keep changes local to your computer for longer durations, its unsafe.
8. Do not format the file using code formatter as this will ruin history of the file. Your code changes will be lost in the formatting changes (which affects complete file). Moreover, you will not be able to take diff of this revision with previous revisions because of white space diffs.

See less