Changes

Once the payload is decided, CELEBRATE. But don't forget to do your service to the next team by documenting the rejected payloads. The factors due to which you rejected some payloads might be irrelevant to the next team's mission and the work done by you on that payload before rejecting it can be helpful to the next team.You can follow the template given below to document your rejected payloads, or create your own.  * Basic Concept of the Payload* Need/Application of the Payload* Points favoring the payload* Analysis done before rejection* Reasons for Rejection* Lessons Learnt* Tips for the next team* Summary