Agile Principles
This principle describes engagement visibility and establishes trust among all internal and external participants.
Transparency
Folks who prioritize the Sprint Backlog, estimate the effort, develop and test software, and identify impediments.
Scrum Team
This high speed event usually lasts between 2-4 weeks.
Sprint
The format is as follows: Who, What, Why or Gain and Understanding
User Story
Each day, all scrum team members meet briefly, 15 minutes or less, to explain to the other members what they worked on the previous day, what they're working on today and what impediments they have.
Daily Stand-Up
A scrum team is know as this if they have a high degree of autonomy and are responsible for the management of their own work.
Self Organizing
Anyone who derives value out of audit in the current cycle.
Stakeholder
The prioritized list of user stories the delivery team commits to working on during a 2-4 week development cycle.
Sprint (or Audit ) Backlog
Used to build out the Story map, this is the high-level component, or defined area, of the audit.
Epic
At the beginning of each sprint, the scrum team meets and determines what user stories will be developed and discuss any logistical issues that will influence the teams successful delivery of features chosen by the team.
Sprint Planning
This agile principle allows for prioritization of risk and drives business value.
Flexible Scope
This role schedules and facilitates internal agile ceremonies as well as ensures clear communication is maintained among everyone involved in the audit.
Scrum Master
The process of ranking the user stories in the audit backlog.
User Story Prioritization
In the beginning of a project the Product Owner is responsible for completing this. The Scrum Team should refer back to this often for reinforcement.
Audit Canvas
This is done once per sprint, where the Scrum Team, Scrum Master, and Product Owner update user stories, refine acceptance criteria, and review user stories for long range sprint planning.
Backlog Refinement
When a user story has been completed to the satisfaction of the Product Owner and meets the objective of the audit with data driven results.
Definition of Done (DoD)
This role sets the direction and vision for the team, prioritizes testing backlog, and communicates final audit report to stakeholders.
Project Champion
This highlights the associated risks and requirements to complete a specific user story.
Acceptance Criteria
This details the project scope and bridges the audit canvas to the user story document.
Story Map
These occur one time per sprint and bring together Subject Matter Experts to engage in an open feedback environment.
Sprint Checkpoint
Agile was born to provide an alternative to this project management approach.
Waterfall
This role understands the value of the audit, eliminates team's impediments and is available to the scrum team in real time everyday, helps plan tests and accepts/rejects workpapers.
Product Owner
Throughout the sprint the scrum team produces these with help from product owner and stakeholders and testing.
Point of View (POV)
This is used to visualize the progress of the audit team and facilitates transparency to the stakeholders regarding emerging Point of Views.
Hypothesis Board
At the end of each sprint, the scrum team meets to discuss what went well, what did not go well and what should be changed.
Sprint Retrospective