Address
Form of work Job description:
Team is able to fully appreciate the power of small, frequent units of value delivery Team is able to analyze their value stream and is able to figure out to improve flow and rapidly remove impediments Team is able to decompose a business ask into several small user stories instead of a mammoth monolithic jira Team is able to vertically slice user stories as needed to enable it to be dev + tested faster Team is able to effective use Jira and other tools to organize work as epics/stories etc Team is able to effectively visualize progress and measure important metrics e.g. Sprint velocity, etc Team is able to groom / refine backlog (sprint and product) and get DOR, DOD, DOA and Acceptance Criteria documented for at least 2 sprints in advance Team is able to appreciate the need for a shared understanding of DOR, DOD, DOA, Acceptance across Dev, test, Ops Team is able to run effective ceremonies - especially Sprint planning, Backlog grooming, Standups Team is able to express AC idiomatically - e.g. As A <> I want to <> So That <> etc Team is able to express tests in BDD Idiom - e.g. Given When Then Team is able to use BDD frameworks e.g. Behave, Serenity etc to automate the Acceptance criteria Team is able to use TDD/ATDD/BDD techniques to code, test, refactor Team follows good version control and branching practices - e.g. Trunk based dev Team follows good CI practices and at a minimum gets an automated daily build Team follows good CD practices, with deployment automated, and at least one deployment to the QA env daily,
with all code changes from all devs of that scrum Team (esp. scrum leads) are coached on how to bring their users closer to the product and not in a separate "UAT" phase Team (esp. Scrum leads) are coached on how to run their scrum teams effectively - i.e. Scrum Leader Training
Team is able to fully appreciate the power of small, frequent units of value delivery Team is able to analyze their value stream and is able to figure out to improve flow and rapidly remove impediments Team is able to decompose a business ask into several small user stories instead of a mammoth monolithic jira Team is able to vertically slice user stories as needed to enable it to be dev + tested faster Team is able to effective use Jira and other tools to organize work as epics/stories etc Team is able to effectively visualize progress and measure important metrics e.g. Sprint velocity, etc Team is able to groom / refine backlog (sprint and product) and get DOR, DOD, DOA and Acceptance Criteria documented for at least 2 sprints in advance Team is able to appreciate the need for a shared understanding of DOR, DOD, DOA, Acceptance across Dev, test, Ops Team is able to run effective ceremonies - especially Sprint planning, Backlog grooming, Standups Team is able to express AC idiomatically - e.g. As A <> I want to <> So That <> etc Team is able to express tests in BDD Idiom - e.g. Given When Then Team is able to use BDD frameworks e.g. Behave, Serenity etc to automate the Acceptance criteria Team is able to use TDD/ATDD/BDD techniques to code, test, refactor Team follows good version control and branching practices - e.g. Trunk based dev Team follows good CI practices and at a minimum gets an automated daily build Team follows good CD practices, with deployment automated, and at least one deployment to the QA env daily,
with all code changes from all devs of that scrum Team (esp. scrum leads) are coached on how to bring their users closer to the product and not in a separate "UAT" phase Team (esp. Scrum leads) are coached on how to run their scrum teams effectively - i.e. Scrum Leader Training
