This document discusses challenges with traditional development approaches and how adopting Agile practices can help address them. It emphasizes that for Agile to work there needs to be prioritization of requirements, collaboration with customers, and flexibility to change plans. Simply adopting Agile terminology or methods is not enough - there must also be changes to culture, skills, budgets and expectations for Agile to be successful.

1. Making Agile Pay Alas! how deeply painful is all PAYMENT! [email_address]

5. Testing reveals too many problems – cost of rework

7. Enable / work with / assume change

8. Improve levels of inspection/ testing

9. Reduce financial exposure per delivery Agile !!

13. Terminology

14. Religion

16. Business – focused terminology

17. UK culture ..

19. Working software over comprehensive documentation

20. Customer collaboration over contract negotiation

21. Responding to change over following a plan Agilemanifesto.org

23. You’re available to collaborate

24. We keep the plan fluid

27. If you can’t prioritise then (arguably) you have no business case

28. Useful: Imagine if...

30. Planning, estimating, budgeting

31. Managing change – negotiating priorities

32. Managing risk

33. Managing quality.

34. PM Imperatives: Planning OR

36. Context: renegotiating priorities

37. Explicit Trade offs

38. Central log, visible record / history

40. Velocity is known

41. Decision is objective

43. Quality – nature of ‘re-work’

45. Timescales

46. Preventing over-spends

47. Making the transition

49. Not a panacea – culture?

50. Complexity?

51. Skills?

52. Budgets/Expectations?

54. Use the dictionary not a creed..

55. Impact of IT organisation business change

56. Benefits management

57. Agree benchmark/ targets.

59. What will be delivered?

60. How will I know whether you’re on track

61. How will I know that what you’re building will work.

63. Piecemeal technique adoption

65. Easier to get broader support

68. Freedom to honour the ‘spirit’ of the contract

69. Team skill sets

71. Methods are NOT recipes [email_address]