Management Bits and Tips

Your boss needs a report, your boss’s boss needs a report from your boss, your boss’s boss’s boss needs a report from your boss’s boss and so on, and everyone needs it before a certain date or even an hour. No one likes delayed reports and no one likes to write them in a hurry (bit). Use IIRW process, Iterative and Incremental Report Writing (tip).

People feel anxiety when time approaches a deadline and reports are delayed. This affects both who needs to read a report and who needs to write it. So don’t leave report writing to the last hour before deadline to avoid delays. If you are in software industry you probably know about iterative and incremental software development. Apply it to report writing too. Write reports incrementally as soon as you finish a task, subtask or milestone and revise them iteratively. This will also accommodate unexpected risks to report delivery when suddenly another boss is added in the middle of reporting chain and people below have to shift reporting time.

- Dmitry Vostokov @ ManagementBits.com -

Coming Soon:

Crash Dump Analysis for System Administrators

New Magazines:

Debugged! MZ/PE: MagaZine for/from Practicing Engineers

New Books:

Windows Debugging: Practical Foundations

DLL List Landscape: The Art from Computer Memory Space

Dumps, Bugs and Debugging Forensics: The Adventures of Dr. Debugalov

WinDbg: A Reference Poster and Learning Cards

Memory Dump Analysis Anthology, Volume 2

Also available:

Memory Dump Analysis Anthology, Volume 1

New Children's Book:

Baby Turing

This entry was posted on Wednesday, December 19th, 2007 at 4:25 pm and is filed under Management Bits and Tips. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.