#IWish there was another kind of Agile besides just Scrum and Kanban. #RetroOnAgile
— Dan Chuparkoff (@Chuparkoff) January 28, 2018
Agile is about to reach its 20th birthday. Software teams, support teams, and even marketing teams have been practicing its rules and principles for years. These teams have built some amazing products thanks to agile software development practices, but 20 years later, how is agile working out for us all?
To find out, we decided to do a retrospective on agile. We interviewed 650 agile software developers at WebSummit 2017 to get their thoughts on what’s working with agile, what should change, and what they’d like to see in the future. People were engaged, excited, and offered up some amazing feedback. We filled an entire wall with their responses.
Today, we’re opening up our retro on agile on twitter. The #RetroOnAgile hashtag is lighting up. Below we’re sharing some of our favorite hot takes.
But don’t let them have all the fun. Reflect on your agile software development experience and follow these three links:
- Tell us what you like
- Tell us what you don’t like
- Think to the future, and fill in the blanks
Starting with “I like:”
#ILike #noestimates and concentration on flow maximizing instead of resource efficiency. #RetroOnAgile
— Toivo Vaje (@ToivoVaje) January 18, 2018
https://twitter.com/PappJeremy/status/954426594914844672
Retrospectives, not just on sprints and projects, but all that we do, are very valuable #justdoit #retroonagile https://t.co/BWJE1FLSUn
— Andrew Kucharski (@akucharski) January 2, 2018
#ILike potential to set sprint goals small enough to present them on Sprint demo #RetroOnAgile
— Dastin Sandura (@dastin_it) January 19, 2018
– #ILike the Accountability! #RetroOnAgile https://t.co/ZQEDd9TP3S
— IFRAH WAQAR (@IfrahWaqar) January 12, 2018
And “I wish:”
Starting with our personal favorite:
#IWish that James Brown knew about @Atlassian's Jira. #RetroOnAgile pic.twitter.com/Jn1vVQdByu
— Dan Chuparkoff (@Chuparkoff) January 24, 2018
#IWish it would be easier to sell #agile development. There’s still too much upfront planning and too little adapting to new information. #RetroOnAgile
— Toivo Vaje (@ToivoVaje) January 18, 2018
#IWish Teams won't declare agile victory prematurely by merely doing stand-ups.
Unless we invest in:
a) a single prioritized backlog
b) KPIs and a DoD that we can get behind, and
c) feel empowered,standing up won't help. We might as well sit and do some work. #RetroOnAgile pic.twitter.com/3ou448YLbw
— Juni Mukherjee ☀️ (@JuniTweets) January 23, 2018
https://twitter.com/JeromeR/status/954067103870484480
#IWish there was a shared, ethical definition of “done done” for ML/AI features in agile projects.#RetroOnAgile https://t.co/Twr8daFj3E
— Dan Massey (@KinkSpring) January 10, 2018
Finally, “What if:”
#WhatIf we stopped worrying about whether tools, practices, or people are Agile or not, and instead kept an open mind about new ideas that can help us work better together. #RetroOnAgile
— Ian Buchanan (@devpartisan) January 24, 2018
#Whatif we could say in 12 months from know that 2018 was the year when #agile was eventually applied to business at large – on all levels, beyond software projects? #RetroOnAgile https://t.co/lyylkPgNeV
— swarmOS (@swarmOS_de) January 10, 2018
https://twitter.com/jmfunk87/status/948240729599610880
https://twitter.com/jmfunk87/status/954785228995751936
Tax breaks, to increase adoption 😆
— Patrick Driscoll (@DrisSkull) January 10, 2018
Join the conversation:
Reflect on your software development experience and participate in the retro on twitter:
- Tell us what you like
- Tell us what you don’t like
- Think to the future, and fill in the blanks