{"id":16,"date":"2026-03-26T16:22:10","date_gmt":"2026-03-26T16:22:10","guid":{"rendered":"https:\/\/agile.powellcrew.us\/?p=16"},"modified":"2026-03-26T16:22:10","modified_gmt":"2026-03-26T16:22:10","slug":"more-on-iterations-and-velocity","status":"publish","type":"post","link":"https:\/\/agile.powellcrew.us\/?p=16","title":{"rendered":"More on Iterations and Velocity"},"content":{"rendered":"

Iterations, truly defined, are ‘idea to successful deployment’.\u00a0 This concept will apply at various levels.\u00a0 An overall application of the iterative process is a high level start to finish accomplishment.\u00a0 Business has an idea of how things can work.\u00a0 Requirements are gathered… communicated.\u00a0 Work is done and deployed to QA, UAT.\u00a0 Deployed to production and verified.. Voila, we have an iteration.\u00a0 Anything that disrupts that smooth process (lol) decreases velocity.\u00a0 Whether it is management, communication, watched pots, personal grudges.. you name it.<\/p>\n

On a different level, an iteration can be defined at more of a micro level… micro-iterations.\u00a0 A developer gets a requirement, makes changes, tests (hopefully, maybe… well it compiles anyway) sends it to the QA team… it comes back.\u00a0 \u00a0Maybe the developer didn’t have the right requirements, maybe bad testing, maybe changes in requirements, maybe the inability to test because of lack of a good test environment.\u00a0 Whatever the reason, we are back to square 1.05.\u00a0 \u00a0Here are a few suggestions of how to increase this velocity…<\/p>\n

    \n
  1. Set up a good test environment with reasonably comprehensive data.<\/li>\n
  2. If release to QA environment is laborious, as it often is, developer can communicate and demonstrate results to QA with a simple 5 minute screen-share.<\/li>\n
  3. Emphasize developer testing… require screen shots of results on tickets.<\/li>\n<\/ol>\n

    More coming…<\/p>\n

     <\/p>\n","protected":false},"excerpt":{"rendered":"

    Iterations, truly defined, are ‘idea to successful deployment’.\u00a0 This concept will apply at various levels.\u00a0 An overall application of the iterative process is a high level start to finish accomplishment.\u00a0 Business has an idea of how things can work.\u00a0 Requirements are gathered… communicated.\u00a0 Work is done and deployed to QA, UAT.\u00a0 Deployed to production and […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-16","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/agile.powellcrew.us\/index.php?rest_route=\/wp\/v2\/posts\/16","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/agile.powellcrew.us\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/agile.powellcrew.us\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/agile.powellcrew.us\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/agile.powellcrew.us\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=16"}],"version-history":[{"count":1,"href":"https:\/\/agile.powellcrew.us\/index.php?rest_route=\/wp\/v2\/posts\/16\/revisions"}],"predecessor-version":[{"id":17,"href":"https:\/\/agile.powellcrew.us\/index.php?rest_route=\/wp\/v2\/posts\/16\/revisions\/17"}],"wp:attachment":[{"href":"https:\/\/agile.powellcrew.us\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=16"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/agile.powellcrew.us\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=16"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/agile.powellcrew.us\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=16"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}