Living Documentation

Correct Answer: Start by documenting the present state of the system and follow an iterative approach for documentation of past changes as per their relevance

The best approach when working in an agile environment is to start by documenting the present state of the system and following an iterative approach for documentation of past changes as per their relevance. This approach accommodates the agile principle of responding to changes over following a plan because it begins by understanding the current state of the system, and then iteratively documenting past changes in order of importance. This makes sense considering the agile practices of incremental improvements and iterative development. The other options are unproductive or counterproductive for the following reasons: Ignoring the previous work and focusing on documenting the new changes only wouldn't help understand the current state and relevance of the previous changes. Postponing the documentation process until all changes are finished goes against the agile principle of continuous improvement and the iterative approach. Asking the team to stop changes in the system till you catch up with documentation not only halts progress but also goes against the very ethos of the agile process which is responsiveness to change.

Correct Answer: Adopt the practice of documentation pruning, which ensures keeping the document lean and regularly updating it to remove any irrelevant or outdated information

The best course of action in this scenario is to 'Adopt the practice of documentation pruning, which ensures keeping the document lean and regularly updating it to remove any irrelevant or outdated information'. This is considering there's no need to maintain outdated or irrelevant information as it can lead to confusion and avoidable complexities. It also helps to optimize system performance and keeps the development team focused. The other answers are not efficient approaches. 'Leave the document as it is, since documenting every change is mandatory' is not a viable solution as it will exacerbate the issue and further degrade system performance. 'Delegate documentation management to another team' merely shifts the problem to another group without addressing the root cause. 'Delete the parts of the documentation that seem unnecessary' might cause the loss of important information as the necessity of the content can't possibly be known for certain without reviewing it.

Correct Answer: Clarify the concept of 'just enough' documentation in Agile, ensuring relevant and needed information is documented without the process becoming too time-consuming or bulky

In Agile methodologies, it is important to maintain the balance between adequate documentation and sustainability. Agile recognizes that comprehensive documentation does not necessarily align with customer satisfaction or product usability. Hence, 'just enough' documentation signifies that only relevant and necessary information that adds value to the project should be documented. This will also ensure that time is spent effectively without making the process bulky or overly time-consuming. Therefore, the strategy should be to clarify the concept of 'just enough' documentation in Agile to the new team member. On the other hand, asking the team member to follow his way and create detailed documents for every aspect could disrupt the agile workflow and may not add value. Ignoring his suggestion completely may lead to lack of mutual respect and communication within the team, which is again against agile principles. Asking him to quit due to difference in practices is not a healthy or professional approach. Adapting to agile from traditional project management can take time and patience.