アジャイルなふりかえり
ふりかえりとは、将来を改善するためにチームが過去について考える時間のことです。技術チームと技術以外のチームの間で、あらゆる問題をふりかえることができます。現在、アジャイルソフトウェア開発に関するふりかえりを公開しています。皆さんの考えをボードに追加して、アジャイルの未来についての定義にぜひ参加してみてください。
#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 の原則の最後の部分には次のように書かれています。
「チームは、より効果的なチームになるための方法を定期的に検討し、それに従って行動を変更、調整します」
アジャイルマニフェストには、チームがアジャイルの価値を最大限に生かすために、定期的にミーティングを行って調整する必要がある、と明確に書かれています。ほとんどの場合、開発チームは、定期的なふりかえりミーティングを開いてこの原則を適用しています。このページでは主にそのようなミーティングに焦点を当てていますが、ふりかえりのやり方はこれだけではありません。
最近では、ふりかえりの概念は、開発チームからビジネスやチームワークのあらゆる分野へと広がりました。
キャンペーンのふりかえりを行うマーケティングチームもあれば、大規模なプレゼンテーションのふりかえりを行う管理チームもあります。さらに、アトラシアンは業界全体のふりかえりミーティングを開催しています。ふりかえりに対するこのオープンな姿勢と、ビジネスのあらゆる分野への広がりは、まさに目を見張るものがあります。
ふりかえりミーティングの魅力は、ふりかえりこそがアジャイルの出発点になるという点です。アジャイルマニフェストの主要概念の多くは、ふりかえりミーティングによって強化されました。考慮するのは次のような価値です。
- 個々のスタッフとプロセスやツールを介したインタラクション
- 計画に従うことによる変化への対応
生身の人間と協力し、変更や改善を行う、文字どおり、これがふりかえりのすべてを表しています。これ以外にアジャイルの原則を強めるものはほとんどありません。ここまでで、ふりかえりが持つ重要性を理解しました。この後は、自分でミーティングを開く方法について説明していきます。
ふりかえりは物事を改善するためのものであることを忘れないでください。アジャイルに興味をお持ちの場合は、#RetroOnAgile に参加して、ソフトウェア開発の未来を一緒に定義していきましょう。
購読
#RetroOnAgile やその他のアジャイルトレンドを常に把握する
ふりかえりミーティング
ふりかえりは、アジャイルチームが自身を評価し、今後の改善に向けた計画を作成する絶好の機会です。継続的な改善を理想とするふりかえりを行うことで、作業サイクルの外に出て過去を振り返り、自己満足という落とし穴を回避できます。
ふりかえりミーティングには、次のような目的があります。
- 前回のスプリント、イテレーション、作業項目の実施状況を評価する (具体的には、チームのダイナミクス、プロセス、ツールを中心に)
- うまく行った項目とそうでなかった項目を明確にしてランク付けする
- チームの作業方法を改善するための計画を作成して実装する
ふりかえりは、内省と適応に落ち着いて集中できる場所です。ふりかえりを成功させるには、すべてのチームメンバーが参加できるような (ただし強制はしない) 雰囲気が必要です。
ふりかえりは、チームをポジティブにし、活気づけるものである必要があります。そうすることで、チームメンバーが重要なフィードバックを共有し、フラストレーションを解消し、協力してソリューションを考案できるようになります。進行役は、チームがどのように連携したか、前回のスプリントにはどのような課題 (および成功) があったかについて理解を深められるなど、ふりかえりから多くのことも得られます。ふりかえりが成功すると、チームメンバーが次のスプリントで担当し、取り組む改善点のリストを作成できます。
初回のふりかえりの実施方法
ふりかえりの実施方法を変更することが有益になることもありますが (詳細は後述)、タイミング、出席者、全般的な進め方など一定の部分については可能な限り一貫性を保つ必要があります。
タイミング:
従来の 2 週間のスプリントで作業しているアジャイルチームの場合、各スプリントの最後にふりかえりを実施します。よりカンバン風の作業スタイルをとっているチームの場合は、月ごと、または四半期ごとのふりかえりの方がより有益な場合があります。また、大規模なイニシアチブが展開された後は、より広範なリーダーシップメンバーを参加させることをおすすめします。成果物よりも、チームがどのように連携してそれを作成したかに焦点を当てるようにしましょう。
スプリントの長さと対象となる範囲に応じて、30 分から 1 時間の間の長さになるように計画を立てます。
参加者:
ふりかえりにはチームメンバー全員が参加し、進行役が話し合いを進めていきます。進行役は、スクラムマスターやプロダクト所有者が務めたり、チーム全体で交代で務めたりします。デザイナー、マーケティング担当者、現在のスプリントやイテレーションに参加した人であれば、誰が担当しても構いません。
内容:
ふりかえりにはいくつかのテーマ (後述) を組み合わせられますが、ふりかえりミーティングの基本的なテンプレートとして以下のようなものが挙げられます。
- うまくいったことと改善できることの簡単なリストを作成する - このリストは、ホワイトボードや Atlassian Confluence ページで作成できるほか、壁に付箋を貼っても作成できます。最初のフィードバックをどこに書き留めるかに関係なく、ミーティング後には必ずメモし、後で参照できるようにします。
- チームにとっての重要度でリストに優先順位を付ける - 共通のテーマが見つかれば、グループ化してもいいでしょう。
- 「改善の余地」リストの上位 2 つの項目を改善する方法と戦術について話し合う - アクション、人、過去ではなく、成果に焦点を当てます。
- アクションプランを作成する - セッションの終了までに、改善部分に対処するための、所有者を明確にしたアクションプランを作成し、期限を決めます。
- #4 を確実に実行する - ふりかえりのたびに同じ問題が持ち出されることほどフラストレーションがたまることはありません。次に行うべきことをすべての参加者が明確に理解するよう徹底して、停滞 (およびフラストレーション) を回避します。ふりかえりで特定した各アクション項目には、完了までを担当する所有者を明確に設定する必要があります。
多様性こそが活力の源
ふりかえりの標準化は、一貫性を保ち、作業中にチーム内での信頼を築く、おすすめの手段です。しかし、さらなるインサイトを明らかにしたり、新しいチームメンバーの参加を促したり、単純にふりかえりのおもしろさを維持したりするために、進行役が「微調整」を行う場合もあります。
外部の進行役を招く - 通常、ふりかえりを進めるのはスクラムマスターかプロジェクトリーダーですが、次回のふりかえりにはゲストを招いて進行してもらってはいかがでしょうか。「個人的な関与」を持たない第三者が話し合いを進行すると、前向きな動きがもたらされることがあります。この戦略はさらに、組織内の人間が他のアジャイルチームのやり方を見ることで、自分のチームに役立つベストプラクティスを見つけられるという効果もあります。
リストの質問を変更する - ふりかえりは、最終的には、機能していることと機能していないことを明らかにすることを目的としています。そのようなときは、次に挙げる質問を使用してみてください。
- 開始/停止/継続: チームが実行を開始、停止、継続する必要がある項目を挙げます。「停止」列の項目を中止する方法に焦点を当てます。
- 増やす/減らす: チームが増やすべき行動と、減らすべき行動を挙げます。「減らす」リストの上位の項目に取り組む方法を計画します。
- うれしい/悲しい/腹立たしい: チームのうれしい、悲しい、腹立たしいを引き起こした原因を挙げます。その原因を推測し、次回は項目がうれしいの列のみになるように、悲しいと腹立たしいのリストとその改善方法に焦点を当てます。
リーダーシップを執る - 大きなプロジェクトを実施した後には、1 時間ほどの時間を設定して、リーダーシップチームのメンバーとともにチームの連携状況について話し合います (個々のイニシアチブの状況ではなく)。
たくさんの改善方法がありますが、独自の新しいやり方を採用しても構いません。分散したチームをまとめる場合であっても、停滞したふりかえりプロセスを改善する場合であっても、重要なことは、チームを関与させ、成果を実行可能なものにすることです。
会話に参加する
以上が、ふりかえりの実施方法の基本です。ご自身のチームのふりかえりについても、ぜひお聞かせください。ツイートの場合は、「I like」、「I wish」、「What if」で書き始めてください。そうすると、上のバーチャル掲示板にあなたのフィードバックが表示されます。会話に参加する →
Jira Software を使用したスクラムの学習
スクラムプロジェクトの推進、バックログの優先順位付けとスプリントへの整理、スクラムセレモニーの実行などの操作をすべて Jira で行う方法を説明するステップバイステップのガイドです。
このチュートリアルを読むアジャイルでよく行われるふりかえりの手順 | アトラシアン
典型的なチームのふりかえりの手順とバリエーション。今ではソフトウェアチームだけでなく、アジャイル開発者にも人気があります。
この記事を読む