Can you be agile and compliant?
summary
Company moves a 100‑strong Product Delivery team from waterfall to agile in January 2015, reorganising into ~5–6‑person feature teams, adding a UX team, a cross‑team release board and quarterly release train cadence. They replace heavy paperwork by linking JIRA stories to FishEye/Crucible code reviews, automated tests and Confluence reports, effectively jettisoning 75% of QMS documentation and pushing automation. Auditors run from story to code to test and return silence — regulated audits pass and delivery speed and traceability measurably improve.
AI-written summary · about
chapters (8)
- 0:00Start
- 22:07Conditions of Satisfaction
- 26:16Confluence Report
- 27:01The Dynamics of the Feature Team
- 31:11Skype for Business
- 36:49Communication Agile
- 37:55Automation
- 38:47Agile Compared to the Waterfall Approach
related talks
44mScaling Agile With a Super-Effective Global Delivery Machine
18mManaging Change
40mMoving from the License Raj to Light Touch Agile Governance
43mFrom an Agile Team to an Agile Organization
37mFrom Waterfall to Agile
30mING's Journey to Agile
45mAgile Alchemy: Balancing Flexibility and Compliance in Software Development
33mThe Agile Way to Add Sec, Dev & Ops into Waterfall