{"id":443,"date":"2024-06-04T09:02:04","date_gmt":"2024-06-04T08:02:04","guid":{"rendered":"http:\/\/localhost:8082\/?p=443"},"modified":"2024-11-02T23:44:42","modified_gmt":"2024-11-02T23:44:42","slug":"tuning-your-agile-framework-for-high-performance-development","status":"publish","type":"post","link":"http:\/\/localhost:8082\/2024\/06\/04\/tuning-your-agile-framework-for-high-performance-development\/","title":{"rendered":"Tuning your agile framework for high-performance development"},"content":{"rendered":"\n<p>Software requirements are a key enabler to high-performing teams, and it\u2019s fair to say I\u2019ve never encountered an underperforming development team that didn\u2019t also have a requirements problem. However, software requirements are only as good as the process they are used in, and you would be forgiven for believing that more detailed requirements fix everything. The situation is more complicated than that.<\/p>\n\n\n\n<p>Defining the right requirements, at the right time, to the right level of detail, for the development team you have, is the skill of software requirements. It\u2019s like getting the timing right when dancing the tango. You need to know when to define epics at a roadmap level, when to write user stories, when to refine them with the technical team, what detail to include, and what to leave unsaid.<\/p>\n\n\n\n<p>Here are a few tried and tested suggestions to get you started, applicable across various types of agile:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>User stories should focus on what the software needs to do, rather than how it should be done (leave that up to the developers to decide).<\/li>\n\n\n\n<li>Acceptance criteria usually make up 80% of a story\u2019s content. <\/li>\n\n\n\n<li>A developer and tester should review each user story, and only once both are satisfied, should the story be considered ready for development. <\/li>\n\n\n\n<li>Decide if stories must be refined outside of the current sprint, or if they can be picked up and refined at any point. <\/li>\n\n\n\n<li>Avoid writing stories too far in advance and deliberately keep the backlog small.<\/li>\n<\/ul>\n\n\n\n<p>A well-functioning agile process is the foundation for better software requirements and high-performing teams, and this requires tailoring your agile framework to the <a href=\"https:\/\/jimmyco.io\/jimmy-thinks\/context\/\">organisational context<\/a> in which your team works.<\/p>\n\n\n\n<p>Established environments should be familiar with agile software development, and tailoring will be focused on fine-tuning rather than wholesale coaching and education. Expect to spend your time addressing items coming out of retrospectives. Emerging environments, on the other hand, may require significant education and coaching before agile working is even possible. However, efforts to educate stakeholders and embed agile working are well spent, even enjoyable, in the company of receptive colleagues. <\/p>\n","protected":false},"excerpt":{"rendered":"<p>Software requirements are a key enabler to high-performing teams, and it\u2019s fair to say I\u2019ve never encountered an underperforming development team that didn\u2019t also have a requirements problem. However, software requirements are only as good as the process they are used in, and you would be forgiven for believing that more detailed requirements fix everything. [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[18,26,17],"tags":[],"class_list":["post-443","post","type-post","status-publish","format-standard","hentry","category-agile","category-legacy-system-replacement","category-software-requirements","missing-thumbnail"],"_links":{"self":[{"href":"http:\/\/localhost:8082\/wp-json\/wp\/v2\/posts\/443","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/localhost:8082\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/localhost:8082\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/localhost:8082\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/localhost:8082\/wp-json\/wp\/v2\/comments?post=443"}],"version-history":[{"count":7,"href":"http:\/\/localhost:8082\/wp-json\/wp\/v2\/posts\/443\/revisions"}],"predecessor-version":[{"id":1043,"href":"http:\/\/localhost:8082\/wp-json\/wp\/v2\/posts\/443\/revisions\/1043"}],"wp:attachment":[{"href":"http:\/\/localhost:8082\/wp-json\/wp\/v2\/media?parent=443"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/localhost:8082\/wp-json\/wp\/v2\/categories?post=443"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/localhost:8082\/wp-json\/wp\/v2\/tags?post=443"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}