Why not Agile?
summary
Reports from Poland show only three agile teams or lawyers while counsel has worked on 80–100 large IT projects and found none agile. Main barriers are procurement focused on price, lack of authorized decision makers inside teams causing stalled migrations, and regulatory guidance that omits agile like KNF recommendations. Agile contracting looks legally similar to waterfall, requires about 10 billable hours of legal work to set terms, and fee structures must include a clear cap to satisfy management boards.
AI-written summary · about
chapters (6)
- 0:00Wprowadzenie
- 1:34INCOMPETENCE COVER-UP
- 4:24DIFFICULT TO PURCHASE
- 6:09ORGANISATIONAL STRUCTURE
- 8:33UNPREDICTABLE BUDGET
- 9:54REGULATORY CONSTRAINTS
related talks
40mMoving from the License Raj to Light Touch Agile Governance
50mWhy Agile Doesn't Scale & What You Can Do About It
34mHow to screw Agile and digital transformation
44mDragging out and failing Agile Transformation – reasons
43mWhy Agile transformation fail
05mFrAgile - lessons from a failed agile transformation
44mCan you be agile and compliant?
01h 10mAgile in the 'Bloody Enterprise'