2013:from_plans_to_capabilities
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| 2013:from_plans_to_capabilities [2012/11/10 07:15] – created jonjagger | 2013:from_plans_to_capabilities [2016/06/11 14:05] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 9: | Line 9: | ||
| Agile can be seen as a shift from planning towards a more capability based way of solving problems. Different agile approaches balance planning and capability in different ways. Many agile adoptions fail because of a conflict between a planning mentality in the organization and the more capability based mindset in agile. The relationship between agile and planning is evolving with ever more capability based approaches gaining in popularity. The goal of the presentation is to show how you should let your context guide the amount of planning you need in your software development process. You will also learn to tell the the difference between a Chuck Norris and a Cowboy process. \\ | Agile can be seen as a shift from planning towards a more capability based way of solving problems. Different agile approaches balance planning and capability in different ways. Many agile adoptions fail because of a conflict between a planning mentality in the organization and the more capability based mindset in agile. The relationship between agile and planning is evolving with ever more capability based approaches gaining in popularity. The goal of the presentation is to show how you should let your context guide the amount of planning you need in your software development process. You will also learn to tell the the difference between a Chuck Norris and a Cowboy process. \\ | ||
| \\ | \\ | ||
| + | Roger: might make a nice pair with Ewan's "Agile Contracts" | ||
| + | Asti: maybe. the proposal isn't really grabbing me \\ | ||
2013/from_plans_to_capabilities.1352531734.txt.gz · Last modified: 2016/06/11 14:05 (external edit)