Agile Retrospectives
回顾是指您的团队反思过去以改善未来的任何时候。在技术团队和非技术团队之间,您几乎可以回顾任何东西!目前,我们正在针对敏捷软件开发进行公开回顾。通过向我们的看板添加一些想法,帮助定义敏捷的未来。
加入 #RetroOnAgile 对话
用 #RetroOnAgile 发推文来回顾您的软件开发情况。用 #ILike 告诉我们您喜欢的一件事,用 #IWish 告诉我们您希望改进的一件事,用 #WhatIf 告诉我们您对未来的期待。可以参考以下数百个回复作为灵感。您的反馈将在 24 小时内显示在此处。
专业提示:^^^ 用您的答案替换问题,留下主题标签 ;-)
#ILike - having iterative development and useful product for users early and often https://t.co/Q1G3SMJoAz #RetroOnAgile
— Amy Patenaude (@LadyEngr802) April 16, 2018
#ILike the conversations that we have as a result of our agile process, which help us clarify assumptions and gaps in reasoning #RetroOnAgile
— Esther Lucia (@NearSideSays) April 16, 2018
#ILike working smarter and seeing solutions evolve through collaboration #RetroOnAgile
— Richard Coen (@RichardCoen9) April 13, 2018
If nothing else, I feel like I waste less time, using the agile process. I know within a few weeks, I'll get feedback on the direction I'm headed with a project. #RetroOnAgile
— Shaun Cave (@Yungdaht) April 13, 2018
#ILike to help people grow and to watch teams develop from a bunch of individuals into a team that takes over responsibility #RetroOnAgile
— Susanne Wesner (@SusanneWesner) April 13, 2018
#Ilike to work in a truly agile way. Enabling and empowering the teams is a powerful way to get your projects rolling. #RetroOnAgile
— Nicolai Kohlbauer (@niggls) April 13, 2018
#ILike - that I can express myself based on agile principles and values #RetroOnAgile
— Rose (@Mmallow91) April 13, 2018
#ILike The dent #agile methodology created in the software universe. https://t.co/VB1RLjxiDI #RetroOnAgile #Mozilla @DuckDuckGo @mozilla @Jira @Atlassian @TheASF
— Aishwary Shrivastava (@toxicaishwary) April 13, 2018
#ILike to work in a interdisciplinary team. Working together with people from other fields toward a common business goal is an amazing experience. #RetroOnAgile
— Rene Grohmann (@GrohmannRene) April 12, 2018
#ILike the Agile principles and values. #RetroOnAgile
— Amy Neil (@MomofXandM) April 12, 2018
#ILike that the focus of software development has changed from deliver software to deliver value. #RetroOnAgile #agile
— Ormycita (@mjormy) April 12, 2018
#ILike companies and CEOs like @peax_ch which are not afraid, to trust and to have confidence in their employees - giving them the chances to establish an agile culture to improve the development process #RetroOnAgile
— Ivan (@IvanAschwanden) April 12, 2018
#RetroOnAgile is a way for my #clockit team to unwind and make the next sprint better. Works amazingly well and puts down everyone's guard. #Jira #ILike
— ClockIt (@clockitio) April 12, 2018
#ILike - To see how team members have open and sincere conversations thinking together how to improve as a team #RetroOnAgile
— Antonio Valle (G2) (@avallesalas) April 12, 2018
#ILike The way agile pushes you to question the way yo do things an helps you improve constantly #RetroOnAgile
— Gonzalo Martín (@gmartinerro) April 12, 2018
#ILike - the willingness to continuously improve and try new things #RetroOnAgile
— Matthew Ho (@inspiredworlds) March 27, 2018
#ILike that our agile process involves hypotheses, experimentation, measurement, and outcomes other than "we've shipped it". #RetroOnAgile
— Mike Melnicki (@mikemelnicki) March 22, 2018
#ILike ability to change the direction, whenever it is reasonably justified #RetroOnAgile
— Kayyak A.K.A kayyaK (@pwysota) March 21, 2018
#ILike the attitude that we never settle. In the spirit of Continuous Improvement we always look for ways to surpass our past achievements. #RetroOnAgile
— Toivo Vaje (@ToivoVaje) January 26, 2018
#ILike that agile allows us to quickly react to changes in the SEO environment. SEO is always unpredictable to a degree. Agile comes with the necessary flexibility to adapt.#RetroOnAgile
— Kevin_Indig (@Kevin_Indig) March 26, 2018
#ILike - Going experimental on our process by trying new things on a frequent basis and holding regular retrospectives to validate our experiments. #RetroOnAgile
— Kent Gillenwater (@KentGillenH2O) March 22, 2018
#ILike that agile encourages teams to focus more on collaboration and outcomes, rather than tools and process #RetroOnAgile
— Kevin Bui (@BuiWonder) March 22, 2018
#ILike that we have people from different knowledge areas working together, in one team, towards a shared outcome #RetroOnAgile
— Kevin Bui (@BuiWonder) March 22, 2018
#ILike Our software team is starting to deliver software by working together #RetroOnAgile
— GerbenH (@Sjampster) March 21, 2018
#ILike deep involvement and awareness of the team that gives unexpected valuable insights #RetroOnAgile
— Nikita Martynov (@nikitokinito) February 22, 2018
#ILike that I can configure Jira to influence how are team runs agile, not just configure it to reflect how we already work. #RetroOnAgile
— Bill Cushard (@billcush) February 14, 2018
#ILike measuring success by outcomes and not outputs #RetroOnAgile https://t.co/YVD5bX83kr
— ʟᴜᴅɪᴠɪɴᴇ ꜱɪᴀᴜ (@lu_syo) February 6, 2018
#ILike that agile provides a means for saying "no" to the urgent, and empowers a team to focus on the important. We are an #agilemarketing team that runs scrum in #jira not a software dev team, for what that's worth. #RetroOnAgile
— Bill Cushard (@billcush) February 14, 2018
#ILike transparency, united team and shared expectations #RetroOnAgile
— Kote Khutsishvili (@kkhutsishvili) February 5, 2018
#ILike it when my team doesn't finish the #Agile Sprint objectives and I make them demo broken shit to all the stakeholders anyway, because of course, public shaming is a powerful motivator. Wait, did I say that out loud? #RetroOnAgile
— Dan Chuparkoff (@Chuparkoff) January 31, 2018
#ILike that DevOps is a thing, just not the watered down “devs do ops” version many teams and companies adopt.#RetroOnAgile https://t.co/Twr8daFj3E
— Dan Massey (@KinkSpring) January 10, 2018
#ILike Daily standups #RetroOnAgile
— Dominik Bułaj (@DominikBulaj) January 17, 2018
#ILike #SpecificationByExample to build quality into software from the start. #RetroOnAgile
— Ian Buchanan (@devpartisan) January 18, 2018
- #ILike the Accountability! #RetroOnAgile https://t.co/ZQEDd9TP3S
— Ifrah Waqar (@IfrahWaqar) January 12, 2018
#ILike potential to set sprint goals small enough to present them on Sprint demo #RetroOnAgile
— KuwałekDastin (@dastin_it) January 19, 2018
#ILike #noestimates and concentration on flow maximizing instead of resource efficiency. #RetroOnAgile
— Toivo Vaje (@ToivoVaje) January 18, 2018
#ILike how Agile keeps my brother and I developing as fast we can #RetroOnAgile
— Troy Taylor (@troystaylor) January 19, 2018
#ILike how we’ve embraced a mindset of solving customer problems to shape how we work over just shipping features. #RetroOnAgile
— jeremyp (@PappJeremy) January 19, 2018
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 we pull up our Jira board during standups to make sure we stay on topic and talk about what we are actually working on. Makes it go faster as opposed to people trying to remember what they are working on #RetroOnAgile
— Alex (@aortiz1989) January 24, 2018
#ILike it when we have a StandUp meeting and when the thing you say you are trying to finish today is already a JIRA ticket. #RetroOnAgile pic.twitter.com/0F1fDHeNpN
— Dan Chuparkoff (@Chuparkoff) January 24, 2018
#ilike if my team was a little less, delivery focused; and a little more sprint focused. #RetroOnAgile
— Tehseen (@syyed51) January 25, 2018
I like how scrum turns agile back into a heavyweight process with lots and lots of meetings, even when those meetings take place in Jira itself.
— Rob Lang (@robbytwitin) January 20, 2018
#ILike it when tasks in a sprint can be completely done by a single person in less than 3 days. #RetroOnAgile
— Dan Chuparkoff (@Chuparkoff) January 26, 2018
#IWish Agile was re-branded/re-named so people don't assume it means "work really fast without thinking". #RetroOnAgile
— *。・゚✧。Michelle・゚✧。・*゚ (@mvenetucci) April 14, 2018
#IWish - It was easier to work with scrum when you are doing devops as by the book you really can't https://t.co/IN3MEnbUf6 #RetroOnAgile
— Mikael Nilsson (@LordNilsson) April 16, 2018
#iwish people would realise agile is not a switch you can turn on overnight #retroOnagile
— Richard Coen (@RichardCoen9) April 16, 2018
#IWish more companies and people understood that Agile can be other methodologies besides Scrum #RetroOnAgile
— Jackie Katsianas (@JackieK_) April 15, 2018
#IWish we could bring the whole company onto the agile practice #RetroOnAgile
— Esther Lucia (@NearSideSays) April 16, 2018
#IWish for Agile we had interactive digital wall boards to use across sites and with people working remotely #RetroOnAgile
— John Kirk (@JDKirk76) April 14, 2018
#IWish - Jira had a blocked status for all issue types, by default. https://t.co/QoOPxf4dys #RetroOnAgile
— David Horton (@hortonda) April 16, 2018
#Iwish there was a broadly adopted standard for assigning and tracking tasks -- that worked across multiple platforms #retroonagile
— F. Guess (@ms_g_austex) April 13, 2018
#IWish 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. #RetroOnAgile
— Michael Benz (@focbenz) April 13, 2018
#Iwish for Enterprises to embrace change and and allow agile ways of working without fearing loss of power and control. #RetroOnAgile
— Nicolai Kohlbauer (@niggls) April 13, 2018
#IWish - we would enable everyone to join and share our #agile methods and not only chosen ones #RetroOnAgile
— Rose (@Mmallow91) April 13, 2018
#Iwish agile wasn't used for micro-management and witch-hunting in the work place #RetroOnAgile
— I T E B A (@iteba) April 13, 2018
#IWish - I wish that being agile was given greater priority than doing agile https://t.co/gSR9z0esIu #RetroOnAgile
— Dev (@DevChatters) April 12, 2018
#IWish we were beyond wondering "how to do Agile the right-way"… it's an idea to work towards vs something to attain quickly & easily #RetroOnAgile
— Mark Opalski (@markopalski) April 12, 2018
#IWish for processes to work for the people, rather than the people working for the processes https://t.co/cdM03j1mZ6 #RetroOnAgile
— Olivier Fortier (@ofortier) April 12, 2018
#IWish companies would not only use the buzzword agile to make the company more interesting to applicants but instead would really support the agile principles. #RetroOnAgile
— Rene Grohmann (@GrohmannRene) April 12, 2018
#IWish - One thing I'd like to see improve is the use of Agile principles by leadership teams. https://t.co/iVBTiXeKcN #RetroOnAgile
— Tina M Marquez (@TinaMMarquez) April 12, 2018
#IWish - What's one thing you wish you could improve about your agile practice? https://t.co/GW2FqwepfL #RetroOnAgile speed up test automation creation with CI/CD
— YouScreenWriter.com (@YouScreenWriter) April 12, 2018
#IWish more folks followed the Agile principles and values rather than trying to hammer away on process and methodology. #RetroOnAgile
— Amy Neil (@MomofXandM) April 12, 2018
#IWish
— grumbly_frown (@grumbly_frown) April 13, 2018
Redraft those ridiculous, self-contradictory 12 commandments so they actually mean something useful
#RetroOnAgile
#IWish - Agile would be used more outside dev teams #RetroOnAgile
— Alex Constantinescu (@alexluchian88) April 12, 2018
#RetroOnAgile #IWish there was more management-focused material available on the transition from waterfall to Agile.
— Steve Harper (@Sharper_pm) April 12, 2018
#IWish companies were more aware of the kind of autonomy and discipline #agile requires #RetroOnAgile
— Ormycita (@mjormy) April 12, 2018
#IWish - Teams respect Retros, do not skip them, make great contributions and integrate #Kaizen cycles when the problem to solve deserves it #RetroOnAgile
— Antonio Valle (G2) (@avallesalas) April 12, 2018
#IWish Agile could be accepted company-wise, and not only in dev teams. #RetroOnAgile
— Gonzalo Martín (@gmartinerro) April 12, 2018
#IWish - Card movement and comments actually talked to my chat client; not my email, not a room #RetroOnAgile
— Josh Smith (@joshsmith01) April 12, 2018
#IWish - I wish to have epics progress bars - they would help in #agile https://t.co/DrY9OC7qOu #RetroOnAgile
— Oleksandr (@Oleksan23251466) April 12, 2018
#IWish - Agile development would take pity on documentation and QA teams, being more specific about how to accommodate doc and test within a sprint. #RetroOnAgile
— BarbaraLGreen (@BarbaraLGreen) April 11, 2018
#IWish - What's one thing you wish you could improve about your #agile practice? https://t.co/M8fBklybbH #RetroOnAgile I wish we could stop the "Agile my way" practices that are not really Agile.
— Gilaine Schneider (@Theodora26) April 11, 2018
#RetroOnAgile #IWish team members could accept the mindset of Agile more than the method argument.
— Marty Talbott (@TalbottMD) April 10, 2018
#iwish to spend less time on Jira to get the desired information and more time doing my job. #RetroOnAgile
— Franck Grimonpont (@chtitter) April 13, 2018
#IWish - we could talk to more teams internally and externally about how to improve our agile practices and how they do their best work #RetroOnAgile
— Matthew Ho (@inspiredworlds) March 27, 2018
#IWish the agile community would explore new techniques for project estimation since story points and planning poker is not cutting it. Possibly this? -> https://t.co/1EX2bWE8Ys #RetroOnAgile
— Mike Melnicki (@mikemelnicki) March 22, 2018
#IWish companies, teams, evangelisers, etc. would not use Agile as #buzz and #MagicWand, but indeed maintain culture #RetroOnAgile
— Kayyak A.K.A kayyaK (@pwysota) March 21, 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 to show pull requests in #Confluence #RetroOnAgile
— Ghost (@Ghost_MAL) March 29, 2018
#IWish more SEOs in the industry would embrace the agile methodology and step away from the waterfall model.#RetroOnAgile
— Kevin_Indig (@Kevin_Indig) March 26, 2018
#IWish "agile" wasn't such a scary word to teams and companies that haven't embraced it #RetroOnAgile
— Kevin Bui (@BuiWonder) March 22, 2018
Ok #IWish that we would focus less on tools and more on interactions and communication #RetroOnAgile 😀
— Peter Sandberg (@patelikestotalk) January 26, 2018
#IWish there was another kind of Agile besides just Scrum and Kanban. #RetroOnAgile
— Dan Chuparkoff (@Chuparkoff) January 28, 2018
#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
#IWish my past experience of Agile had not made me wary of self-proclaimed "Agile Advocates" #RetroOnAgile
— ʟᴜᴅɪᴠɪɴᴇ ꜱɪᴀᴜ (@lu_syo) February 6, 2018
#Iwish jira could make coffee #RetroOnAgile pic.twitter.com/y8pQsqpmul
— gonelf (@gonelf) March 7, 2018
#IWish Jira could make customizing release notes simpler #RetroOnAgile
— Krishnanand Nayak (@pedavan) March 7, 2018
#iwish I could have a better view of all projects, including sorting, prioritisation, labeling, and client assigning. #RetroOnAgile
— Darren Pinder (@dmpinder) March 7, 2018
#IWish - A less clunky mechanism for injecting 'Business as Usual' into the development stream. #RetroOnAgile
— Kent Gillenwater (@KentGillenH2O) March 22, 2018
#IWish JIRA tied usability defects to their originating story, and easily graphed it, so Agile teams could focus on usability. #RetroOnAgile pic.twitter.com/It0NAcb9Bo
— Jerome (@JeromeR) January 18, 2018
#Iwish to have more advance functions in jql.
— Loshy Chandran (@loshyc) March 7, 2018
ADFS authenticatin - please release id-79 asap.
#IWish the assignee could be shared among team members, so that pair programming can be planned in advance 😀 #RetroOnAgile
— Rick Patci (@ThePatci) January 18, 2018
- #IWish Retrospective would magically appear linked to related issues in the new sprint and help overcome scope creep! #RetroOnAgile https://t.co/w6c4gOddfk
— Ifrah Waqar (@IfrahWaqar) January 22, 2018
#IWish we could keep TLMs from degenerating into program managers. #RetroOnAgile
— Juni Mukherjee (@JuniTweets) January 23, 2018
"When agile shops were first being established, an important consideration was to keep TLMs from having full visibility into any one agile team." https://t.co/32eiK5ih9a
#IWish @JIRA would let me story point my sub-tasks and roll up the points. Purist is not always pragmatic. #RetroOnAgile
— Kyle Rozendo (@RozendoZA) January 23, 2018
#IWish Consensus would work always. Sadly, the voting environment could get polluted. #RetroOnAgile
— Juni Mukherjee (@JuniTweets) January 23, 2018
"Even though agile rests on collaboration, the 'agreement by consensus' model has it’s share of flaws, depending on the who, the what, and the when." https://t.co/32eiK5ih9a pic.twitter.com/9X7dFon0RV
#IWish people would move their sub-tasks along the Agile board without having to be reminded #RetroOnAgile
— Diana MacPherson (@dianamacpherson) January 23, 2018
#IWish Teams won't declare agile victory prematurely by merely doing stand-ups.
— Juni Mukherjee (@JuniTweets) January 23, 2018
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
#IWish that stakeholders, peer-reviewers, & quality team-members could star an assignee's work on a ticket. #RetroOnAgile pic.twitter.com/9tqkpSGgyP
— Dan Chuparkoff (@Chuparkoff) January 24, 2018
#IWish Jira was fast
— Bastien Billey 🇫🇷 (@billey_b) January 24, 2018
#iwish @jira has "hide fields" option. It is issue-secured now but not field-secured. #RetroOnAgile
— Rajinikanth (@Demiracer) January 21, 2018
It would be super awesome to allow my customers to vote on JIRAs without eating up a license for login #RetroOnAgile @JIRA #JiraOnDemand https://t.co/Yj2fwz7DQq
— Eddie Weakley (@3weakley) January 6, 2018
#retroonagile I wish people played as a team. No aggressive jira Tix allowed
— Sean Regan (@seanjregan) January 25, 2018
#IWish there was out-of-the-box integration between my automated unit tests and the columns of my scrum board. #RetroOnAgile
— Dan Chuparkoff (@Chuparkoff) January 31, 2018
#IWish we are not surprised that the feature does not work during demo and be more in control #RetroOnAgile
— GerbenH (@Sjampster) March 21, 2018
#WhatIf we could make our agile board three dimensional? What other dimension would we add? #RetroOnAgile
— Esther Lucia (@NearSideSays) April 16, 2018
#WhatIf The whole company practiced Agile, not just the developers? What would our teams look like? What could our teams accomplish? #RetroOnAgile
— Nicole Gagliardi (@_nlg_) April 13, 2018
#WhatIf #agile teams wouldn't loose the big picture due to a flatened backlog, and be reminded how #UserStories are interrelated (e.g. from #UX point of view or from #BusinessProcess perspective) ? #RetroOnAgile
— Christophe THIERRY (@chthierry) April 13, 2018
#Whatif we dare to trust and take the prime directive seriously not only for retro but for every day live #RetroOnAgile
— Susanne Wesner (@SusanneWesner) April 13, 2018
#Whatif the agile way of getting things done would be taught very early on and would be the core of the way we get things done? #RetroOnAgile
— Nicolai Kohlbauer (@niggls) April 13, 2018
#whatif, The way I seek Agile working in the next few years is having to accommodate BOT coders as part of the squad and dealing with BOT communication too #RetroOnAgile
— Duane Gomes (@GomesDuane) April 12, 2018
#WhatIf Some agile techniques were taught early in schools so kids could benefit from them and learn how to plan their homework efficiently #RetroOnAgile
— Gonzalo Martín (@gmartinerro) April 12, 2018
#whatIf certifications weren't the criteria for hiring #agile practitioners #RetroOnAgile
— Ormycita (@mjormy) April 12, 2018
I’d replace the word software with product in the manifesto #RetroOnAgile
— Matthew Evans (@matthewevansrec) April 13, 2018
#WhatIf - We get so used to automation that we forget that bots do not participate in retros? #RetroOnAgile
— Antonio Valle (G2) (@avallesalas) April 12, 2018
#WhatIf we didn't try to manage multiple products at once on multiple boards with a single #Agile team? #RetroOnAgile
— le Violon Chocolat (@ViolonChocolat) April 12, 2018
#WhatIf there was one menu where you could easily navigate between boards in JIRA? #RetroOnAgile
— Melissa Gill (@lligassilem) April 12, 2018
#WhatIf we ran daily sprints? would we have daily retros? #RetroOnAgile
— Matthew Ho (@inspiredworlds) March 27, 2018
#WhatIf the software industry moved from delivery of projects to delivery of outcomes? https://t.co/btLBb3fhU4 #RetroOnAgile @Atlassian
— Mike Melnicki (@mikemelnicki) March 22, 2018
#WhatIf every user story was treated as an experiment and it's impact easily measured #RetroOnAgile
— Kent Gillenwater (@KentGillenH2O) March 22, 2018
#WhatIf we would keep agility rather that DO Agile? Plus we should mind that it require a lot of self-discipline. #RetroOnAgile
— Kayyak A.K.A kayyaK (@pwysota) March 21, 2018
#WhatIf Scrum and Kanban weren't the only ways to be agile? #RetroOnAgile
— Kevin Bui (@BuiWonder) March 22, 2018
#WhatIf we collectively decided that Sprints were, at most, one day from start to finish. #ContinuousAgile #YourStandupIsAlreadyYourPlanningMeetingAndYourDemo #RetroOnAgile
— Dan Chuparkoff (@Chuparkoff) February 1, 2018
#WhatIf SEOs would work in agile sprints like developers?#RetroOnAgile
— Kevin_Indig (@Kevin_Indig) March 26, 2018
#WhatIf humans just be humans and bots did all the technical (or remaining) stuff (or vice-versa?) #RetroOnAgile
— Homero Leal (@homerojleal) March 22, 2018
#WhatIf DevOps was its own Value Stream?#RetroOnAgile
— A9 Group, Inc. (@a9consulting) January 2, 2018
#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 stopped using “agile” as a fucking noun. #RetroOnAgile
— Charles Miller (@carlfish) January 6, 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
#WhatIf the agile community treated security and privacy as seriously as they treat daily stand-ups?#RetroOnAgile https://t.co/Twr8daFj3E
— Dan Massey (@KinkSpring) January 10, 2018
#WhatIf there were no estimations??? What a Merry Christmas it would be!! #RetroOnAgile https://t.co/j9zmtrcXvz
— John Funk (@jmfunk87) January 20, 2018
#WhatIfEverybodyMovedToKanban #RetroOnAgile Kanban has changed our processes and efficiency for the better.
— John Funk (@jmfunk87) January 2, 2018
#WhatIf we stopped trying to make Agile fit with top-down management, budget-driven planning, and feature-bloated products? #RetroOnAgile
— Ian Buchanan (@devpartisan) January 12, 2018
#WhatIf(Companies stopped investing on precise projects scope and rather invested in trusting capable agile teams who will deliver value continuously?) #RetroOnAgile
— Adil Chahid (@AdilusPrimus) January 30, 2018
#WhatIf a user could report a ticket in one language and @Atlassian's Jira could show it to the team in a second language? #RetroOnAgile pic.twitter.com/qPWDfpgcMG
— Dan Chuparkoff (@Chuparkoff) January 25, 2018
#WhatIf @Atlassian's JIRA could use estimate the probability that a checked in block of code would get reopened based on machine-learned, correlated factors. #RetroOnAgile pic.twitter.com/vQ8DTrzrWm
— Dan Chuparkoff (@Chuparkoff) January 26, 2018
为什么要进行回顾?
2001 年,我们开始了敏捷回顾。敏捷开发十二项原则中最后一项内容如下:
“团队会定期思考如何提高效率,然后相应地调整其行为。”
敏捷宣言明确指出:为了充分践行敏捷价值观,团队应定期开会回顾并进行调整。最常见的是,开发团队通过定期举办回顾会议来应用这一原则,虽然该会议是本页大部分内容的重点,但这并不是唯一的回顾方式。
最近,回顾的概念已经脱离了开发团队,进入了业务和团队合作的各个方面。
我知道营销团队回顾营销活动,管理团队回顾大型演示文稿,更重要的是,Atlassian 针对所在的整个行业进行回顾。这种对回顾的开放态度以及业务各方面激增的回顾,令人非常兴奋。
回顾最让人感到兴奋的是,它们是开始敏捷旅程的地方。敏捷宣言中的许多核心概念都通过回顾性会议得到了加强。考虑以下价值:
- 个人和交互优先于流程和工具
- 响应变化优先于遵循计划
从表面上看,这就是回顾的全部意义:与真实的人合作进行变更和改进。强化敏捷原则效果非常好。既然我们已经知道回顾为何如此重要,请继续阅读并学习如何自己举办回顾会议。
别忘了,我们进行回顾是为了让事情变得更好,因此,如果您喜欢敏捷,请参与我们的 #RetroOnAgile 并帮助定义软件开发的未来。
订阅
及时了解 #RetroOnAgile 和其他敏捷趋势
回顾性会议
通过回顾,您的敏捷团队可以进行自我评估并制定计划以解决未来需要改进的领域。回顾通过走出工作周期来反思过去,拥抱持续改进的理念,并防止自满情绪的陷阱:
回顾会议的目的是:
- 评估上一个冲刺、迭代或工作项目的进展情况,特别是围绕团队动态、流程和工具。
- 阐明和堆叠对进展顺利的项目以及那些表现不佳的项目进行排名。
- 制定并实施改善团队工作方式的计划。
回顾为专注于内省和适应提供了一个安全的场所。为了使回顾取得成功,需要营造一种支持性的氛围,鼓励(但不强迫)所有团队成员做出贡献。
对于您的团队来说,回顾应该是一次积极、充满活力的体验。它可以帮助团队成员分享重要的反馈,不受挫折影响,共同努力提出解决方案。主持人还可以从回顾中获得很多好处,包括更好地了解团队如何协作以及他们在上次冲刺中经历了哪些挑战(和成功)。成功的回顾会产生一系列改进,团队成员将在下一次冲刺中掌握并努力实现这些改进。
如何进行第一次回顾
虽然改变回顾的形式可能是有益的(下文将详细介绍!),某些方面,例如时间、参与者和一般形式,应尽可能保持一致。
时间:
对于在传统的两周冲刺中工作的敏捷团队,回顾应在每个冲刺结束时举行。对于工作风格更像看板的团队来说,每月或每季度进行一次回顾可能更有意义。重大计划推出后,让更多领导层成员参与进来也很合理;注意不要关注交付的内容,而要关注团队如何共同努力产生这些成果。
计划花费至少三十分钟,最多一个小时,具体取决于冲刺的时间和您必须覆盖的量。
人员:
每位团队成员都应参加回顾,由主持人主持讨论。主持人可以是 Scrum 大师、产品负责人,也可以由团队成员轮流担任。设计人员、营销人员或其他为当前冲刺或迭代做出贡献的人均可自由参加。
内容:
有几种方法可以混合您的回顾(我们将在下面讨论),但以下是回顾性会议的基本模板:
- 创建一份简短的列表,列出行之有效的内容和可以改进的内容。此列表可以在白板上、Atlassian Confluence 页面上创建,甚至可以在墙上的便利贴上创建!无论您在哪里捕捉到最初的反馈,一定要在会议结束后立即记住,供以后参考。
- 按团队的重要性来确定此列表的优先级。您可能会发现一些共同的主题,这些主题可以组合在一起。
- 讨论“改进余地”列表上前两项的改进方法和策略。关注结果,而不是操作、人或过去。
- 制定行动计划。会议结束时,团队应该提出一些可行的想法,明确负责人和到期时间,以解决需要改进的领域。
- 严格执行第四条。没有什么比在每一次回顾中重复同样的障碍更令人沮丧的了。确保每个人都有明确知道后续步骤,从而避免停滞(和沮丧!)。回顾中确定的每个操作项目都应有一个明确的负责人,负责跟踪直到项目完成。
因为多样性让生活更美好
标准化回顾是一个好主意,可以随着时间的推移在团队之间建立一致性并构建信任。但是,主持人可以尝试一些“调整”,这些调整可能有助于发现更多见解,鼓励新团队成员的参与,或者只是保持其趣味性。
请一位外部主持人。通常,回顾由 Scrum 大师或项目主管主持,但您可以考虑邀请一位嘉宾来主持下一次回顾。如果让没有“项目相关利益”的人来主持讨论,动态可能会发生积极的变化。此外,这种策略使组织内的其他人能够观察其他敏捷团队的工作情况,并可能为自己的团队选择一些最佳实践。
改变列表提示。归根结底,回顾旨在揭示哪些方案有效,哪些无效。请考虑以下不同的提示:
- 开始/停止/继续:团队应该开始做什么、停止做什么,然后继续做什么。关注停止“停止”列中的项目的方法。
- 多/少:团队需要多做和少做的事情。围绕如何处理“少做”列表中的热门项目制定计划。
- 高兴/悲伤生气:什么让团队感到高兴、悲伤和生气。猜对了,重点关注悲伤和生气的列表以及如何改进,这样下次就只有高兴一列有项目了。
让领导层参与进来。重大项目推出后,与您的领导团队成员安排一个小时,重点关注团队的合作方式(而不是计划进展的细节)。
有很多方法可以改进,所以不要犹豫,寻找自己的新技巧。无论您是想让分散的团队参与进来,还是要改进停滞不前的回顾流程,关键是要保持团队的参与度并使结果切实可行。
加入对话!
既然您已经了解了进行回顾的基础知识,我们很乐意听听您关于自己团队回顾的看法。用“我想要”或“如果”开始您的推文,您可能会在上方的虚拟板上看到您的反馈!加入对话 →
通过 Jira Software 了解 Scrum
分步指南,说明如何在 Jira 中推动 Scrum 项目、排定待办事项的优先级并将其整理为冲刺、运行 Scrum 仪式,等等。
阅读本教程How to Run an Agile Retrospective Meeting with Examples
Instructions and variations on the classic team retrospective. Popular with agile developers, but not just for software teams anymore.
阅读这篇文章