Project Management

Please login or join to subscribe to this thread

Have you ever experienced negative consequences from too little or too much documentation?

linkedin twitter facebook   Agile   Ethics   Risk Management  
avatar
Stelian ROMAN Project Manager| MicroSafety Carlingford, New South Wales, Australia

One of the most persistent misconceptions about Agile methodologies is that "Agile means no documentation." This misunderstanding can have serious ethical and practical consequences for teams, organizations, and stakeholders. Agile values "working software over comprehensive documentation," as stated in the Manifesto for Agile Software Development, but this does not mean documentation is absent or unimportant. Moreover, the Manifesto was written for software development, and although most of the values and principles can be extrapolated for product development in general, the authors may not have considered product development in highly regulated environments, such as medical devices. Rather, Agile encourages documentation that delivers true value, supports collaboration, and enables responsible professional conduct. This post explores the ethical dimensions of documentation practices in Agile contexts.

Blog post: The Ethics of Documentation in Agile: Debunking the "No Documentation" Myth

ProjectManagement.com - The Agile Enterprise

Please login or join to reply

Content ID:
ADVERTISEMENTS

I hope, when they die, cartoon characters have to answer for their sins.

- Jack Handey

ADVERTISEMENT

Sponsors