diff options
| author | Christian Cleberg <[email protected]> | 2024-05-01 21:45:52 -0500 |
|---|---|---|
| committer | Christian Cleberg <[email protected]> | 2024-05-01 21:45:52 -0500 |
| commit | 7d3b5175f2d9d016b06190273fcfeb380a460b3f (patch) | |
| tree | 71139c9021b09704b2d45be3b64d54e2acbae55f /content/blog/2023-08-18-agile-auditing.md | |
| parent | 7c70a351e25106ceff49ff8ee0a38e2a545f62f0 (diff) | |
| download | cleberg.net-7d3b5175f2d9d016b06190273fcfeb380a460b3f.tar.gz cleberg.net-7d3b5175f2d9d016b06190273fcfeb380a460b3f.tar.bz2 cleberg.net-7d3b5175f2d9d016b06190273fcfeb380a460b3f.zip | |
prettier formatting and rewrap lines
Diffstat (limited to 'content/blog/2023-08-18-agile-auditing.md')
| -rw-r--r-- | content/blog/2023-08-18-agile-auditing.md | 34 |
1 files changed, 17 insertions, 17 deletions
diff --git a/content/blog/2023-08-18-agile-auditing.md b/content/blog/2023-08-18-agile-auditing.md index 66f6570..e1b60c4 100644 --- a/content/blog/2023-08-18-agile-auditing.md +++ b/content/blog/2023-08-18-agile-auditing.md @@ -52,20 +52,20 @@ processes and controls at hand. Audit Examples: -- Engagement teams must value the team members, client contacts, and their - interactions over the historical processes and tools that have been used. -- Engagement teams must value a final report that contains sufficient audit - documentation over excessive documentation or scope creep. -- Engagement teams must collaborate with the audit clients as much as feasible - to ensure that both sides are constantly updated with current knowledge of the - engagement's status and any potential findings, rather than waiting for - pre-set meetings or the end of the engagement to communicate. -- Engagement teams must be able to respond to change in an engagement's - schedule, scope, or environment to ensure that the project is completed in a - timely manner and that all relevant areas are tested. - - In terms of an audit department's portfolio, they must be able to respond - to changes in their company's or client's environment and be able to - dynamically change their audit plan accordingly. +- Engagement teams must value the team members, client contacts, and their + interactions over the historical processes and tools that have been used. +- Engagement teams must value a final report that contains sufficient audit + documentation over excessive documentation or scope creep. +- Engagement teams must collaborate with the audit clients as much as feasible + to ensure that both sides are constantly updated with current knowledge of + the engagement's status and any potential findings, rather than waiting for + pre-set meetings or the end of the engagement to communicate. +- Engagement teams must be able to respond to change in an engagement's + schedule, scope, or environment to ensure that the project is completed in a + timely manner and that all relevant areas are tested. + - In terms of an audit department's portfolio, they must be able to + respond to changes in their company's or client's environment and be + able to dynamically change their audit plan accordingly. # Scrum @@ -74,9 +74,9 @@ how an audit team can potentially mold that mindset into the audit world, but how does a team implement these ideas? There are many methods that use an Agile mindset, but I prefer -[Scrum](https://en.wikipedia.org/wiki/Scrum_(software_development)). Scrum is a -framework based on Agile that enables a team to work through a project through a -series of roles, ceremonies, artifacts, and values. +[Scrum](<https://en.wikipedia.org/wiki/Scrum_(software_development)>). Scrum is +a framework based on Agile that enables a team to work through a project through +a series of roles, ceremonies, artifacts, and values. Let's dive into each of these individually. |
