Agile retrospectives: Use the past to define the future
Was this helpful?
Was this helpful?
Agile was re-branded/re-named so people don't assume it means "work really fast without thinking". — *｡･ﾟ✧｡Michelle･ﾟ✧｡･*ﾟ (@mvenetucci)
- It was easier to work with scrum when you are doing devops as by the book you really can't — Mikael Nilsson (@LordNilsson)
people would realise agile is not a switch you can turn on overnight — Richard Coen (@RichardCoen9)
more companies and people understood that Agile can be other methodologies besides Scrum — Jackie Katsianas (@JackieK_)
we could bring the whole company onto the agile practice — Esther Lucia (@NearSideSays)
for Agile we had interactive digital wall boards to use across sites and with people working remotely — John Kirk (@JDKirk76)
- Jira had a blocked status for all issue types, by default. — David Horton (@hortonda)
there was a broadly adopted standard for assigning and tracking tasks -- that worked across multiple platforms — F. Guess (@ms_g_austex)
it would be easier to fuel the agile spirit from inside the teams to invest the energy from that better in good practices and software instead of having to discuss processes. — Michael Benz (@focbenz)
for Enterprises to embrace change and and allow agile ways of working without fearing loss of power and control. — Nicolai Kohlbauer (@niggls)
- we would enable everyone to join and share our methods and not only chosen ones — Rose (@Mmallow91)
agile wasn't used for micro-management and witch-hunting in the work place — I T E B A (@iteba)
- I wish that being agile was given greater priority than doing agile — Dev (@DevChatters)
we were beyond wondering "how to do Agile the right-way"… it's an idea to work towards vs something to attain quickly & easily — Mark Opalski (@markopalski)
for processes to work for the people, rather than the people working for the processes — Olivier Fortier (@ofortier)
companies would not only use the buzzword agile to make the company more interesting to applicants but instead would really support the agile principles. — Rene Grohmann (@GrohmannRene)
- One thing I'd like to see improve is the use of Agile principles by leadership teams. — Tina M Marquez (@TinaMMarquez)
Redraft those ridiculous, self-contradictory 12 commandments so they actually mean something useful
Unless we invest in: a) a single prioritized backlog b) KPIs and a DoD that we can get behind, and c) feel empowered,
- What's one thing you wish you could improve about your agile practice? speed up test automation creation with CI/CD— YouScreenWriter.com (@YouScreenWriter)
more folks followed the Agile principles and values rather than trying to hammer away on process and methodology. — Amy Neil (@MomofXandM)
— grumbly_frown (@grumbly_frown)
- Agile would be used more outside dev teams — Alex Constantinescu (@alexluchian88)
there was more management-focused material available on the transition from waterfall to Agile.— Steve Harper (@Sharper_pm)
companies were more aware of the kind of autonomy and discipline requires — Ormycita (@mjormy)
- Teams respect Retros, do not skip them, make great contributions and integrate cycles when the problem to solve deserves it — Antonio Valle (G2) (@avallesalas)
Agile could be accepted company-wise, and not only in dev teams. — Gonzalo Martín (@gmartinerro)
- Card movement and comments actually talked to my chat client; not my email, not a room — Josh Smith (@joshsmith01)
- I wish to have epics progress bars - they would help in — Oleksandr (@Oleksan23251466)
- Agile development would take pity on documentation and QA teams, being more specific about how to accommodate doc and test within a sprint. — BarbaraLGreen (@BarbaraLGreen)
- What's one thing you wish you could improve about your practice? I wish we could stop the "Agile my way" practices that are not really Agile.— Gilaine Schneider (@Theodora26)
team members could accept the mindset of Agile more than the method argument.— Marty Talbott (@TalbottMD)
to spend less time on Jira to get the desired information and more time doing my job. — Franck Grimonpont (@chtitter)
- we could talk to more teams internally and externally about how to improve our agile practices and how they do their best work — Matthew Ho (@inspiredworlds)
the agile community would explore new techniques for project estimation since story points and planning poker is not cutting it. Possibly this? -> — Mike Melnicki (@mikemelnicki)
companies, teams, evangelisers, etc. would not use Agile as and , but indeed maintain culture — Kayyak A.K.A kayyaK (@pwysota)
it would be easier to sell development. There’s still too much upfront planning and too little adapting to new information. — Toivo Vaje (@ToivoVaje)
to show pull requests in — Ghost (@Ghost_MAL)
more SEOs in the industry would embrace the agile methodology and step away from the waterfall model.— Kevin_Indig (@Kevin_Indig)
"agile" wasn't such a scary word to teams and companies that haven't embraced it — Kevin Bui (@BuiWonder)
Ok that we would focus less on tools and more on interactions and communication 😀— Peter Sandberg (@patelikestotalk)
there was another kind of Agile besides just Scrum and Kanban. — Dan Chuparkoff (@Chuparkoff)
there was a shared, ethical definition of “done done” for ML/AI features in agile projects. — Dan Massey (@KinkSpring)
my past experience of Agile had not made me wary of self-proclaimed "Agile Advocates" — ʟᴜᴅɪᴠɪɴᴇ ꜱɪᴀᴜ (@lu_syo)
jira could make coffee — gonelf (@gonelf)
Jira could make customizing release notes simpler — Krishnanand Nayak (@pedavan)
I could have a better view of all projects, including sorting, prioritisation, labeling, and client assigning. — Darren Pinder (@dmpinder)
- A less clunky mechanism for injecting 'Business as Usual' into the development stream. — Kent Gillenwater (@KentGillenH2O)
JIRA tied usability defects to their originating story, and easily graphed it, so Agile teams could focus on usability. — Jerome (@JeromeR)
to have more advance functions in jql. ADFS authenticatin - please release id-79 asap.— Loshy Chandran (@loshyc)
the assignee could be shared among team members, so that pair programming can be planned in advance 😀 — Rick Patci (@ThePatci)
- Retrospective would magically appear linked to related issues in the new sprint and help overcome scope creep! — Ifrah Waqar (@IfrahWaqar)
we could keep TLMs from degenerating into program managers.
"When agile shops were first being established, an important consideration was to keep TLMs from having full visibility into any one agile team." — Juni Mukherjee (@JuniTweets)
would let me story point my sub-tasks and roll up the points. Purist is not always pragmatic. — Kyle Rozendo (@RozendoZA)
— Juni Mukherjee (@JuniTweets)
people would move their sub-tasks along the Agile board without having to be reminded — Diana MacPherson (@dianamacpherson)
Teams won't declare agile victory prematurely by merely doing stand-ups.
standing up won't help. We might as well sit and do some work. — Juni Mukherjee (@JuniTweets)
that stakeholders, peer-reviewers, & quality team-members could star an assignee's work on a ticket. — Dan Chuparkoff (@Chuparkoff)
Jira was fast— Bastien Billey 🇫🇷 (@billey_b)
has "hide fields" option. It is issue-secured now but not field-secured. — Rajinikanth (@Demiracer)
It would be super awesome to allow my customers to vote on JIRAs without eating up a license for login — Eddie Weakley (@3weakley)
I wish people played as a team. No aggressive jira Tix allowed— Sean Regan (@seanjregan)
there was out-of-the-box integration between my automated unit tests and the columns of my scrum board. — Dan Chuparkoff (@Chuparkoff)
we are not surprised that the feature does not work during demo and be more in control — GerbenH (@Sjampster)