애자일 회고
회고는 팀이 미래를 개선하기 위해 과거를 되돌아보는 시간입니다. 기술 팀과 기술 이외의 팀 사이에서 거의 모든 것에 대해 회고를 진행할 수 있습니다. 현재 Atlassian에서는 애자일 소프트웨어 개발에 대한 공개 회고를 주최하고 있습니다. 보드에 아이디어를 추가하여 애자일의 미래를 정의하도록 도와주세요.
#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년, 공식적인 서명을 통해 애자일 회고가 탄생했습니다. 애자일 개발의 12가지 원칙 중 마지막 원칙은 다음과 같습니다.
"정기적으로 팀은 효과성을 더 높이는 방법을 되돌아본 다음 그에 따라 행동을 수정하고 조정합니다."
애자일 매니페스토를 통해 명확히 알 수 있는 점은, 애자일 가치를 최대한 활용하려면 팀이 정기적으로 회의를 가져 확인하고 조정해야 한다는 것입니다. 가장 일반적으로, 개발 팀은 정기적인 회고 회의를 열어서 이 원칙을 적용합니다. 이 페이지의 많은 부분이 회의에 초점을 두고 있지만 회의가 회고를 진행하는 유일한 방법은 아닙니다.
최근에는 회고의 개념이 개발 팀에서 벗어나 비즈니스 및 팀워크의 모든 측면까지 확장되었습니다.
캠페인에 대해 회고를 진행하는 마케팅 팀, 대규모 프레젠테이션에 대해 회고를 진행하는 관리 팀, 그리고 Atlassian이 업계 전반에서 회고를 주최하고 있다는 것을 알고 있습니다. 회고에 대한 열린 태도와 비즈니스의 모든 측면으로의 확산은 엄청나게 기대할 만한 일입니다.
회고에 대해 기대하는 이유는 애자일이 실제로 진행되는 곳이기 때문입니다. 애자일 매니페스토의 핵심 개념 중 많은 부분은 회고 회의를 통해 강화됩니다. 다음과 같은 가치를 고려해 보세요.
- 프로세스 및 도구보다 개인 및 상호 작용
- 계획을 따르기보다는 변화에 대응
회고란 표면 그대로 실제 관계자들과 협력하여 변화와 개선을 이루는 것이 전부입니다. 회고보다 애자일 원칙을 더 잘 강화해주는 것은 많이 없습니다. 회고가 중요한 이유를 살펴봤으니, 이제 자체적인 회의를 여는 방법을 읽고 알아보세요.
또한 회고를 진행하는 이유는 상황을 개선하기 위한 것이므로, 애자일에 관심이 있다면 #RetroOnAgile에 참여하여 소프트웨어 개발의 미래를 정의하도록 도와주세요.
구독
#RetroOnAgile 및 기타 애자일 트렌드를 파악하세요
회고 회의
회고는 애자일 팀이 스스로를 평가하고 향후 개선 영역을 다루기 위한 계획을 세울 수 있는 좋은 기회입니다. 회고는 과거를 반영하기 위해 작업 주기를 벗어나 지속적인 개선의 이상을 포용하고 현재 상태에 안주하는 것의 위험으로부터 보호합니다.
회고 회의의 목적은 다음과 같습니다.
- 특히 팀 역학, 프로세스 및 도구를 중심으로 마지막 스프린트, 반복 또는 작업 항목이 어떻게 진행되었는지 평가합니다.
- 잘 진행된 항목과 그렇지 않은 항목을 분명하게 표시하고 순위를 매깁니다.
- 팀의 업무 방식을 개선하기 위한 계획을 수립하고 구현합니다.
회고는 자기 성찰과 적응에 집중할 수 있는 안전한 장소를 마련해 줍니다. 회고를 성공적으로 진행하려면 모든 팀원이 기여하도록 장려하는(하지만 강요하지는 않는), 서로를 지지하는 분위기가 필요합니다.
회고는 팀에 긍정적이고 활력을 주는 경험이 되어야 합니다. 회고는 팀원들이 중요한 피드백을 공유하고, 좌절감을 떨쳐 버리고, 함께 협력하여 해결 방법을 생각해내는 데 도움이 됩니다. 진행자는 또한 팀이 함께 일하는 방식과 지난 스프린트에서 경험한 어려움(및 성공)에 대한 더 나은 이해를 포함하여 회고를 통해 많은 것을 얻을 수 있습니다. 회고를 성공적으로 진행하면 팀원들이 소유권을 갖고 다음 스프린트에서 이루고자 하는 개선 사항의 목록이 만들어집니다.
첫 회고를 진행하는 방법
회고의 형식을 변경하는 것은 도움이 될 수도 있지만(자세한 내용은 아래에 나와 있음) 시기, 참석자 및 일반적인 형식과 같은 특정 측면은 최대한 일관성을 유지해야 합니다.
언제:
기존의 2주 스프린트를 사용하는 애자일 팀의 경우 매 스프린트가 끝날 때마다 회고를 진행해야 합니다. 칸반에 더 가까운 스타일로 일하는 팀의 경우 월별 또는 분기별 회고가 더 적합할 수 있습니다. 또한 주요 이니셔티브가 시작된 후 광범위한 리더십의 구성원을 참여시키는 것이 좋습니다. 제공된 결과가 아니라 팀이 함께 협력하여 결과를 만들어낸 방법에 초점을 맞추도록 주의하세요.
스프린트의 길이와 다뤄야 할 양에 따라 최소 30분에서 최대 1시간 정도 할애할 계획을 세우세요.
누가:
논의는 진행자가 주도하며 모든 팀원이 회고에 참석해야 합니다. 진행자는 스크럼 마스터 또는 제품 소유자일 수 있으며, 팀 전체에서 번갈아 가며 맡을 수 있습니다. 디자이너, 마케터 또는 현재 스프린트나 반복에 기여한 다른 관계자를 자유롭게 참여시키세요.
무엇을:
회고에 변화를 주는 방법에는 여러 가지가 있지만(아래에서 설명할 예정) 회고 회의를 위한 기본 템플릿은 다음과 같습니다.
- 잘 진행된 항목과 개선할 수 있는 항목의 간단한 목록을 만듭니다. 이 목록은 화이트보드, Atlassian Confluence 페이지 또는 벽에 붙이는 스티커 메모에도 만들 수 있습니다! 최초 피드백을 어디서 캡처했는지에 관계없이, 나중에 참조할 수 있도록 회의 직후에 기록하세요.
- 하나의 팀으로서 중요도에 따라 목록의 우선 순위를 정합니다. 함께 그룹화할 수 있는 공통적인 주제를 발견하게 될 수도 있습니다.
- "개선의 여지가 있음" 목록에서 상위 두 개의 항목을 개선하는 방법과 전략에 대해 논의합니다. 작업, 팀원 또는 과거가 아닌 결과에 초점을 맞추세요.
- 작업 계획을 세웁니다. 세션이 끝날쯤에, 팀은 개선이 필요한 영역을 다루기 위해 명확한 소유자 및 기한과 함께 몇 가지 실행 가능한 아이디어를 제시했을 것입니다.
- 4번을 실행하는 데 대한 규율을 지킵니다. 모든 회고에서 똑같은 장애물이 반복되는 것보다 더 답답한 일은 없을 것입니다. 모두가 명확한 다음 단계를 파악하도록 하여 정체(및 좌절)를 방지하세요. 회고에서 파악한 각 작업 항목에는 작업을 완료할 때까지 맡아 수행하는 명확한 소유자가 있어야 합니다.
다양성은 삶의 향신료
회고를 표준화하는 것은 일관성을 유지하고 시간이 지남에 따라 팀 간의 신뢰를 쌓는 데 좋은 방법입니다. 그러나 진행자가 몇 가지 "조정"을 시도해볼 수 있으며, 그러면 추가적인 인사이트를 발견하거나, 새로운 팀원의 참여를 장려하거나, 단순히 흥미 있게 유지하는 데 도움이 될 수 있습니다.
외부 진행자를 참여시킵니다. 일반적으로 회고는 스크럼 마스터나 프로젝트 리더가 진행하지만 다음 회고를 유도하기 위해 게스트를 참여시키는 것도 좋을 수 있습니다. "이해 관계가 있는" 관계자가 논의를 이끌도록 하면 상황은 긍정적인 쪽으로 변화할 수 있습니다. 또한 이 전략을 통해 조직 내 다른 직원은 다른 애자일 팀의 작업 방식을 관찰하고 자신의 팀을 위한 몇 가지 모범 사례를 배워갈 수도 있습니다.
목록 프롬프트에 변화를 줍니다. 하루 일과를 마칠 무렵에 하는 회고는 무엇이 효과가 있고 그렇지 않은지 확인하기 위한 것입니다. 다음과 같은 다양한 프롬프트를 고려해 보세요.
- 시작/중단/계속: 팀이 시작하고, 중단하고, 계속해야 할 일입니다. "중단" 열의 항목을 중단하는 방법에 중점을 두세요.
- 더 많이/더 적게: 팀이 더 많이 또는 더 적게 해야 하는 일입니다. "더 적게 할 일" 목록의 상위 항목을 해결할 계획을 세우세요.
- 기쁨/슬픔/화남: 팀을 기쁘고 슬프고 화나게 만든 요인입니다. 짐작할 수 있듯이, 다음 번에는 기쁨 열에만 항목이 있도록 슬픔 및 화남 목록과 개선 방법에 초점을 맞추세요.
리더십 팀을 참여시킵니다. 주요 프로젝트를 시작한 후 리더십 팀원과 1시간 정도의 회의 일정을 잡고 (이니셔티브 진행 방식에 대한 세부 사항이 아닌) 팀이 어떻게 협력했는지에 중점을 두세요.
개선할 수 있는 방법에는 여러 가지가 있으므로 주저하지 말고 나만의 새로운 요령을 찾아보세요. 분산된 팀을 참여시키거나 정체된 회고 프로세스를 개선하려는 경우 핵심은 팀의 참여를 유지하고 실행 가능한 결과를 만드는 것입니다.
대화에 참여하세요!
이제 회고 진행에 대한 기본적인 사항을 알아보았으므로 여러분의 팀의 회고에 대해 들어보고 싶습니다. “I like”, “I wish” 또는 “What if”가 들어간 트윗을 작성하면 위의 가상 보드에서 피드백을 볼 수 있습니다! 대화 참여 →
Jira Software 소프트웨어로 스크럼 배우기
스크럼 프로젝트를 추진하고, 백로그를 우선 순위를 지정하여 스프린트로 구성하고, 스크럼 세레모니를 실행하기 등 모두를 Jira에서 수행하는 방법에 관한 단계별 가이드입니다.
이 자습서 읽기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.
이 문서 읽기