Nowadays, we have jira and confluence to help us managing the task and actual works. However, without good strategy, it can not help much.

Task Type with Expected Outputs

It is important to have clear definition on the expected outputs of each type of tasks.

Task Type Description Expected Outputs
1 Issue Raise Issue to others Email, Error Message, Problem Statement
2 Request Rasie new functions needs to others Problem Statement, Measurement on Success
3 Idea Have something to share Problem Statement, Potential solutions , Documentation
4 Solutioning Idea propose, Communications,  System Designs that is aiming for request Emails , Documentation ,  decomposed of multiple problem statement. each with different solutions
5 Implementation Functions need to be implement PR based on Documentation, CI-Test Pass
6 Runs Run Experiment or Chase other teams progress Experiment result,  Documentation, Config and Metric, With version control that people can check into git-version and reproduce the result.
7 Output for UAT Prepare particular output to external party Feature Dictionary, Data Dictionary, Reports
8 Acquisition Close the deal from UAT or ..etc Confirmation Email
9 Implement to Dev Shipping the project or product. PR,  Documentation of UAT result , Documentation of Model Government + … etc