DISCUSS

According to the readings in the PMBOK guide and my own thoughts, I believe that estimates and predictions in agile techniques appear to lean towards a system that has more flexibility than traditional. There is room to add or remove onto plans, unlike that of traditional. For well-defined predictions and estimates, traditional approach is well suited for this rather than leaving things open for modifications. For preference to approach, I do not think one is better than the other, rather that each has its benefits to be useful for a certain project. So all in all, it will really depend on the project and if the approach should lean more flexible or structured.

If the need to replace traditional methods is necessary, then project teammates/ stakeholders would need to be notified. I have found more success in projects that utilize slow transitions, thus elements that are easiest to modify to the new method should be addressed first. Also, this decision would most likely have been discussed earlier to determine if it is more beneficial for the project, as we would have done a risk vs benefits assessment of sorts. On the bright side, flexibility allows for realistic occurrences such as setbacks and priority changes.

Summarization is key to get a message across in a short format. I would most likely focus on progress and goals achieved/reached then follow up with important or critical next steps. I would have to ensure that the summary doesn't necessarily apply to one department or team section but rather keep it general and one that can apply to all involved in the project. Depending on how quickly information needs to be conveyed, this can be done in anywhere from a brief paragraph summary to something pictorial like a flow chart/diagram.