The document outlines Antonio Cobo's journey discovering Agnostic Agile. It defines Agnostic as being generalized to work across different systems. Agnostic Agile is described as being adaptive to context without prescribing a specific framework. Cobo discusses his background and realization that being pragmatic is more important than dogmatism. He then shares 12 principles of Agnostic Agile, including putting customers first, tailoring agility to context, and acknowledging that dogmatism is non-agile. The talk aims to promote flexibility over rigid frameworks and sharing knowledge.
4. Antonio Cobo @Mind_of_AC
Who has already heard about Agnostic Agile?
http://www.yoyospetsupplies.com.au/ebay/images/cat%20raising%20hand.jpg
5. Antonio Cobo @Mind_of_AC
What is this talk about?
1.Definition of Agnostic
2.My context before
3.Discovering Agnostic Agile
4.The twelve principles
5.Wrapping up
7. Antonio Cobo @Mind_of_AC
Agnostic, in an information technology (IT) context,
refers to something that is generalized so that it
is interoperable among various systems.
The term can refer not only to software and hardware,
but also to business processes or practices
Source: http://whatis.techtarget.com/definition/agnostic
8. Antonio Cobo @Mind_of_AC
“Agnostic Agile” is:
Agility that is adaptive within your given system
according to context and is not by necessity a
prescription of any particular framework or method.
40. Antonio Cobo @Mind_of_AC
3. To tailor agility to context.
Head of Agile Transformation of a medium size financial company.
“First thing I did when I joined this company was to force everybody (even
marketing and sales) to use Scrum. I always do that on every company I work
for, cause I want everybody to know what Agile is”
49. Antonio Cobo @Mind_of_AC
10. To acknowledge that dogmatism is non-agile.
“Scrum is the only sensible way of developing a new product”
50. Antonio Cobo @Mind_of_AC
10. To acknowledge that dogmatism is non-agile.
“Scrum is the only sensible way of developing a new product”
- a Certified Scrum Trainer
52. Antonio Cobo @Mind_of_AC
11. To recognise that there is more to agile than agile.
5 weeks sprints
4 teams performing the standup together
Standups only on Mondays, Wednesdays and Fridays
Physical board with tickets of the 4 teams together (25 people)
Releasing to staging environment only at the end of the 5 weeks sprint
53. Antonio Cobo @Mind_of_AC
11. To recognise that there is more to agile than agile.
5 weeks sprints
4 teams performing the standup together
Standups only on Mondays, Wednesdays and Fridays
Physical board with tickets of the 4 teams together (25 people)
Releasing to staging environment only at the end of the 5 weeks sprint
54. Antonio Cobo @Mind_of_AC
11. To recognise that there is more to agile than agile.
5 weeks sprints
4 teams performing the standup together
Standups only on Mondays, Wednesdays and Fridays
Physical board with tickets of the 4 teams together (25 people)
Releasing to staging environment only at the end of the 5 weeks sprint
• 6-7 months per release
• Releasing to staging after those 6-7 months
• +1 month (or more) for bugs fixing
• Teams not really talking to each other
• No standups or boards
60. Antonio Cobo @Mind_of_AC
Don’t lock your company/customer on one framework
Adapt, inspect, improve
Share knowledge and learn from others
61. Antonio Cobo @Mind_of_AC
Don’t lock your company/customer on one framework
Adapt, inspect, improve
Share knowledge and learn from others
It’s ok to have unknown and ask for help