{"id":3426,"date":"2017-07-03T04:52:59","date_gmt":"2017-07-03T11:52:59","guid":{"rendered":"https:\/\/lookforwardconsulting.com\/?p=3426"},"modified":"2025-09-17T10:06:42","modified_gmt":"2025-09-17T09:06:42","slug":"traditional-functional-technical-documentation-work-agile","status":"publish","type":"post","link":"https:\/\/thescrumacademy.com\/es\/2017\/07\/03\/traditional-functional-technical-documentation-work-agile\/","title":{"rendered":"How does the traditional functional and technical documentation work in Agile?"},"content":{"rendered":"

In Scrum and Agile, there is not much guidance given on functional and technical documentation.\u00a0 The Agile Manifesto<\/a>\u00a0states that Agile teams value “working software over comprehensive documentation.”\u00a0 That provides clear guidance on what is the focus of an Agile team, but is not a helpful answer to the question.<\/p>\n

\n

Looking deeper into the Agile principles<\/a>, the authors of the Agile Manifesto share these two ideas which could be helpful in thinking about documentation: “working software is the primary measure of progress” and “the most efficient and effective method of conveying information to and within a development team is face-to-face conversation.”\u00a0 For people who lack direct experience working with Agile teams, these statements seem to reinforce the myth that documentation is unnecessary for Agile teams.<\/p>\n

However, in my sixteen years of working with Agile teams, this myth is completely untrue.\u00a0 Agile teams have plenty of functional and technical documentation, but it is different than what people expect if their organization has a long history of industrial processes<\/a>.\u00a0 In a traditional organization, most of the documentation for the design, requirements and technical specifications is created up-front and approved BEFORE any code is written.<\/p>\n

Agile teams take a different perspective.\u00a0 Documentation tends to be an outcome of the working software.\u00a0 Since the code is considered the design<\/a>, most of what is needed to document the software, from a technical perspective, will be in the source code and the automated unit tests.\u00a0 This is why Extreme Programming places a strong emphasis on test-driven development and merciless refactoring to achieve a simple design<\/a>.\u00a0 The various automated tests serve as an executable specification<\/a>\u00a0of how the code works with various examples.\u00a0 Some people say these executable tests act like the system specification<\/a>.<\/p>\n

However, not everything one needs to know about the software can be kept in the source code and the tests.\u00a0 High-level design diagrams, design briefs\\narratives, information flows, roadmaps and use cases are examples of other types of the documentation some products find necessary.\u00a0 The amount of documentation an Agile teams needs depends on their domain and consequences of failure (comfort, discretionary money, essential money or life).\u00a0 For these other documents, I recommend creating them incrementally and use them to document what was created, not what is to be built.<\/p>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

In Scrum and Agile, there is not much guidance given on functional and technical documentation.\u00a0 The Agile Manifesto\u00a0states that Agile teams value “working software over comprehensive documentation.”\u00a0 That provides clear […]<\/p>\n","protected":false},"author":1,"featured_media":6493,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"_price":"","_stock":"","_tribe_ticket_header":"","_tribe_default_ticket_provider":"","_tribe_ticket_capacity":"0","_ticket_start_date":"","_ticket_end_date":"","_tribe_ticket_show_description":"","_tribe_ticket_show_not_going":false,"_tribe_ticket_use_global_stock":"","_tribe_ticket_global_stock_level":"","_global_stock_mode":"","_global_stock_cap":"","_tribe_rsvp_for_event":"","_tribe_ticket_going_count":"","_tribe_ticket_not_going_count":"","_tribe_tickets_list":"[]","_tribe_ticket_has_attendee_info_fields":false,"footnotes":""},"categories":[208,7,32,205,22,25,10,77,34,6,24,206,29,214,44,53,75],"tags":[],"class_list":["post-3426","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-advanced-practitioners","category-agile-scrum","category-agile-transformation","category-beginners","category-coaching","category-communication","category-developers","category-distributed-teams","category-documentation","category-extreme-programming","category-legacy-code","category-practitioners","category-product-owner","category-scrum-artifacts","category-scrum-master","category-simple-design","category-stakeholders"],"yoast_head":"\nHow does the traditional functional and technical documentation work in Agile? - The Scrum Academy<\/title>\n<meta name=\"description\" content=\"Carlton Nettleton\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/thescrumacademy.com\/es\/2017\/07\/03\/traditional-functional-technical-documentation-work-agile\/\" \/>\n<meta property=\"og:locale\" content=\"es_ES\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"How does the traditional functional and technical documentation work in Agile? - The Scrum Academy\" \/>\n<meta property=\"og:description\" content=\"Carlton Nettleton\" \/>\n<meta property=\"og:url\" content=\"https:\/\/thescrumacademy.com\/es\/2017\/07\/03\/traditional-functional-technical-documentation-work-agile\/\" \/>\n<meta property=\"og:site_name\" content=\"The Scrum Academy\" \/>\n<meta property=\"article:published_time\" content=\"2017-07-03T11:52:59+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2025-09-17T09:06:42+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/thescrumacademy.com\/wp-content\/uploads\/2017\/07\/Unknowntttt-copy.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"1200\" \/>\n\t<meta property=\"og:image:height\" content=\"949\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Carlton Nettleton\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Escrito por\" \/>\n\t<meta name=\"twitter:data1\" content=\"Carlton Nettleton\" \/>\n\t<meta name=\"twitter:label2\" content=\"Tiempo de lectura\" \/>\n\t<meta name=\"twitter:data2\" content=\"2 minutos\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/thescrumacademy.com\\\/es\\\/2017\\\/07\\\/03\\\/traditional-functional-technical-documentation-work-agile\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/thescrumacademy.com\\\/es\\\/2017\\\/07\\\/03\\\/traditional-functional-technical-documentation-work-agile\\\/\"},\"author\":{\"name\":\"Carlton Nettleton\",\"@id\":\"https:\\\/\\\/thescrumacademy.com\\\/es\\\/#\\\/schema\\\/person\\\/2a0fb199044ecd4af3704c734747fc6a\"},\"headline\":\"How does the traditional functional and technical documentation work in Agile?\",\"datePublished\":\"2017-07-03T11:52:59+00:00\",\"dateModified\":\"2025-09-17T09:06:42+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/thescrumacademy.com\\\/es\\\/2017\\\/07\\\/03\\\/traditional-functional-technical-documentation-work-agile\\\/\"},\"wordCount\":388,\"image\":{\"@id\":\"https:\\\/\\\/thescrumacademy.com\\\/es\\\/2017\\\/07\\\/03\\\/traditional-functional-technical-documentation-work-agile\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/thescrumacademy.com\\\/wp-content\\\/uploads\\\/2017\\\/07\\\/Unknowntttt-copy.jpg\",\"articleSection\":[\"Advanced Practitioners\",\"Agile Scrum\",\"Agile Transformation\",\"Beginners\",\"Coaching\",\"Communication\",\"Developers\",\"Distributed Teams\",\"Documentation\",\"Extreme Programming\",\"Legacy Code\",\"Practitioners\",\"Product Owner\",\"Scrum Artifacts\",\"Scrum Master\",\"Simple Design\",\"Stakeholders\"],\"inLanguage\":\"es\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/thescrumacademy.com\\\/es\\\/2017\\\/07\\\/03\\\/traditional-functional-technical-documentation-work-agile\\\/\",\"url\":\"https:\\\/\\\/thescrumacademy.com\\\/es\\\/2017\\\/07\\\/03\\\/traditional-functional-technical-documentation-work-agile\\\/\",\"name\":\"How does the traditional functional and technical documentation work in Agile? - The Scrum Academy\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/thescrumacademy.com\\\/es\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/thescrumacademy.com\\\/es\\\/2017\\\/07\\\/03\\\/traditional-functional-technical-documentation-work-agile\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/thescrumacademy.com\\\/es\\\/2017\\\/07\\\/03\\\/traditional-functional-technical-documentation-work-agile\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/thescrumacademy.com\\\/wp-content\\\/uploads\\\/2017\\\/07\\\/Unknowntttt-copy.jpg\",\"datePublished\":\"2017-07-03T11:52:59+00:00\",\"dateModified\":\"2025-09-17T09:06:42+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/thescrumacademy.com\\\/es\\\/#\\\/schema\\\/person\\\/2a0fb199044ecd4af3704c734747fc6a\"},\"description\":\"Carlton Nettleton\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/thescrumacademy.com\\\/es\\\/2017\\\/07\\\/03\\\/traditional-functional-technical-documentation-work-agile\\\/#breadcrumb\"},\"inLanguage\":\"es\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/thescrumacademy.com\\\/es\\\/2017\\\/07\\\/03\\\/traditional-functional-technical-documentation-work-agile\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"es\",\"@id\":\"https:\\\/\\\/thescrumacademy.com\\\/es\\\/2017\\\/07\\\/03\\\/traditional-functional-technical-documentation-work-agile\\\/#primaryimage\",\"url\":\"https:\\\/\\\/thescrumacademy.com\\\/wp-content\\\/uploads\\\/2017\\\/07\\\/Unknowntttt-copy.jpg\",\"contentUrl\":\"https:\\\/\\\/thescrumacademy.com\\\/wp-content\\\/uploads\\\/2017\\\/07\\\/Unknowntttt-copy.jpg\",\"width\":1200,\"height\":949},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/thescrumacademy.com\\\/es\\\/2017\\\/07\\\/03\\\/traditional-functional-technical-documentation-work-agile\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/thescrumacademy.com\\\/es\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"How does the traditional functional and technical documentation work in Agile?\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/thescrumacademy.com\\\/es\\\/#website\",\"url\":\"https:\\\/\\\/thescrumacademy.com\\\/es\\\/\",\"name\":\"The Scrum Academy\",\"description\":\"Everyone anywhere can do better Scrum\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/thescrumacademy.com\\\/es\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"es\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/thescrumacademy.com\\\/es\\\/#\\\/schema\\\/person\\\/2a0fb199044ecd4af3704c734747fc6a\",\"name\":\"Carlton Nettleton\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"es\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/6d69c37c349230a49a1ec6c77c21c4b35043de9fbcce8a202d61f707025cd537?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/6d69c37c349230a49a1ec6c77c21c4b35043de9fbcce8a202d61f707025cd537?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/6d69c37c349230a49a1ec6c77c21c4b35043de9fbcce8a202d61f707025cd537?s=96&d=mm&r=g\",\"caption\":\"Carlton Nettleton\"},\"description\":\"My name is Carlton Nettleton and I am the President of Look Forward Consulting. I am an international speaker, trainer and author of the book, Fourteen Observations of Good Scrum Practice and my book has been translated into Spanish. My passion is to share my excitement, enthusiasm and encouragement with teams and organizations as they reach for higher levels of performance and engagement. My business is to help your business grow and flourish.\",\"url\":\"https:\\\/\\\/thescrumacademy.com\\\/es\\\/author\\\/admin\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"How does the traditional functional and technical documentation work in Agile? - The Scrum Academy","description":"Carlton Nettleton","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/thescrumacademy.com\/es\/2017\/07\/03\/traditional-functional-technical-documentation-work-agile\/","og_locale":"es_ES","og_type":"article","og_title":"How does the traditional functional and technical documentation work in Agile? - The Scrum Academy","og_description":"Carlton Nettleton","og_url":"https:\/\/thescrumacademy.com\/es\/2017\/07\/03\/traditional-functional-technical-documentation-work-agile\/","og_site_name":"The Scrum Academy","article_published_time":"2017-07-03T11:52:59+00:00","article_modified_time":"2025-09-17T09:06:42+00:00","og_image":[{"width":1200,"height":949,"url":"https:\/\/thescrumacademy.com\/wp-content\/uploads\/2017\/07\/Unknowntttt-copy.jpg","type":"image\/jpeg"}],"author":"Carlton Nettleton","twitter_card":"summary_large_image","twitter_misc":{"Escrito por":"Carlton Nettleton","Tiempo de lectura":"2 minutos"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/thescrumacademy.com\/es\/2017\/07\/03\/traditional-functional-technical-documentation-work-agile\/#article","isPartOf":{"@id":"https:\/\/thescrumacademy.com\/es\/2017\/07\/03\/traditional-functional-technical-documentation-work-agile\/"},"author":{"name":"Carlton Nettleton","@id":"https:\/\/thescrumacademy.com\/es\/#\/schema\/person\/2a0fb199044ecd4af3704c734747fc6a"},"headline":"How does the traditional functional and technical documentation work in Agile?","datePublished":"2017-07-03T11:52:59+00:00","dateModified":"2025-09-17T09:06:42+00:00","mainEntityOfPage":{"@id":"https:\/\/thescrumacademy.com\/es\/2017\/07\/03\/traditional-functional-technical-documentation-work-agile\/"},"wordCount":388,"image":{"@id":"https:\/\/thescrumacademy.com\/es\/2017\/07\/03\/traditional-functional-technical-documentation-work-agile\/#primaryimage"},"thumbnailUrl":"https:\/\/thescrumacademy.com\/wp-content\/uploads\/2017\/07\/Unknowntttt-copy.jpg","articleSection":["Advanced Practitioners","Agile Scrum","Agile Transformation","Beginners","Coaching","Communication","Developers","Distributed Teams","Documentation","Extreme Programming","Legacy Code","Practitioners","Product Owner","Scrum Artifacts","Scrum Master","Simple Design","Stakeholders"],"inLanguage":"es"},{"@type":"WebPage","@id":"https:\/\/thescrumacademy.com\/es\/2017\/07\/03\/traditional-functional-technical-documentation-work-agile\/","url":"https:\/\/thescrumacademy.com\/es\/2017\/07\/03\/traditional-functional-technical-documentation-work-agile\/","name":"How does the traditional functional and technical documentation work in Agile? - The Scrum Academy","isPartOf":{"@id":"https:\/\/thescrumacademy.com\/es\/#website"},"primaryImageOfPage":{"@id":"https:\/\/thescrumacademy.com\/es\/2017\/07\/03\/traditional-functional-technical-documentation-work-agile\/#primaryimage"},"image":{"@id":"https:\/\/thescrumacademy.com\/es\/2017\/07\/03\/traditional-functional-technical-documentation-work-agile\/#primaryimage"},"thumbnailUrl":"https:\/\/thescrumacademy.com\/wp-content\/uploads\/2017\/07\/Unknowntttt-copy.jpg","datePublished":"2017-07-03T11:52:59+00:00","dateModified":"2025-09-17T09:06:42+00:00","author":{"@id":"https:\/\/thescrumacademy.com\/es\/#\/schema\/person\/2a0fb199044ecd4af3704c734747fc6a"},"description":"Carlton Nettleton","breadcrumb":{"@id":"https:\/\/thescrumacademy.com\/es\/2017\/07\/03\/traditional-functional-technical-documentation-work-agile\/#breadcrumb"},"inLanguage":"es","potentialAction":[{"@type":"ReadAction","target":["https:\/\/thescrumacademy.com\/es\/2017\/07\/03\/traditional-functional-technical-documentation-work-agile\/"]}]},{"@type":"ImageObject","inLanguage":"es","@id":"https:\/\/thescrumacademy.com\/es\/2017\/07\/03\/traditional-functional-technical-documentation-work-agile\/#primaryimage","url":"https:\/\/thescrumacademy.com\/wp-content\/uploads\/2017\/07\/Unknowntttt-copy.jpg","contentUrl":"https:\/\/thescrumacademy.com\/wp-content\/uploads\/2017\/07\/Unknowntttt-copy.jpg","width":1200,"height":949},{"@type":"BreadcrumbList","@id":"https:\/\/thescrumacademy.com\/es\/2017\/07\/03\/traditional-functional-technical-documentation-work-agile\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/thescrumacademy.com\/es\/"},{"@type":"ListItem","position":2,"name":"How does the traditional functional and technical documentation work in Agile?"}]},{"@type":"WebSite","@id":"https:\/\/thescrumacademy.com\/es\/#website","url":"https:\/\/thescrumacademy.com\/es\/","name":"The Scrum Academy","description":"Everyone anywhere can do better Scrum","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/thescrumacademy.com\/es\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"es"},{"@type":"Person","@id":"https:\/\/thescrumacademy.com\/es\/#\/schema\/person\/2a0fb199044ecd4af3704c734747fc6a","name":"Carlton Nettleton","image":{"@type":"ImageObject","inLanguage":"es","@id":"https:\/\/secure.gravatar.com\/avatar\/6d69c37c349230a49a1ec6c77c21c4b35043de9fbcce8a202d61f707025cd537?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/6d69c37c349230a49a1ec6c77c21c4b35043de9fbcce8a202d61f707025cd537?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/6d69c37c349230a49a1ec6c77c21c4b35043de9fbcce8a202d61f707025cd537?s=96&d=mm&r=g","caption":"Carlton Nettleton"},"description":"My name is Carlton Nettleton and I am the President of Look Forward Consulting. I am an international speaker, trainer and author of the book, Fourteen Observations of Good Scrum Practice and my book has been translated into Spanish. My passion is to share my excitement, enthusiasm and encouragement with teams and organizations as they reach for higher levels of performance and engagement. My business is to help your business grow and flourish.","url":"https:\/\/thescrumacademy.com\/es\/author\/admin\/"}]}},"_links":{"self":[{"href":"https:\/\/thescrumacademy.com\/es\/wp-json\/wp\/v2\/posts\/3426","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/thescrumacademy.com\/es\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/thescrumacademy.com\/es\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/thescrumacademy.com\/es\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/thescrumacademy.com\/es\/wp-json\/wp\/v2\/comments?post=3426"}],"version-history":[{"count":0,"href":"https:\/\/thescrumacademy.com\/es\/wp-json\/wp\/v2\/posts\/3426\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/thescrumacademy.com\/es\/wp-json\/wp\/v2\/media\/6493"}],"wp:attachment":[{"href":"https:\/\/thescrumacademy.com\/es\/wp-json\/wp\/v2\/media?parent=3426"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/thescrumacademy.com\/es\/wp-json\/wp\/v2\/categories?post=3426"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/thescrumacademy.com\/es\/wp-json\/wp\/v2\/tags?post=3426"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}