Data Encryption: Your data is protected by end-to-end encryption, both over the wire and at rest. Once the list is ready, the answers can be consolidated into a single chain representing the opinion reached by a common consensus of the group. Use the car brand idea of running a sprint retrospective to relax your teammates. This method is very popular and effective, especially for new teams. Retrospective meetings can be held at various stages during the project: Any retrospective meeting will involve the following steps: #1) What went well, What should have been done better, Action items. What strategies will work to complete the job? Thank you dear readers for your positive feedback :) ! Manage the Entire Scrum Process in One Page. This technique captures feedback using Pluses and Deltas i.e. Right Retrospective questions allow the team to think, at the same time provides an ownership to each team member thus making it truly Agile. This ties into the concept of Continuous … Would you be interested in adding it to your list of formats? Retrium has so many formats that your team will never have the same meeting twice. Nice sum-up of things that matter in retrospectives, thanks Neha! Manage Backlog, Multiple Sprints of different Scrum Roles with a single-page visually executable canvas, Allow instantly access, review and generate scrum artifacts and related documents to be archived in the Shared Cabinet. Reason: No process enforcement- No code freeze. Sprints are at the very heart of scrum and agile methodologies, and getting sprints right will help your agile team ship better software with fewer headaches. It’s simple to gather feedback asynchronously or in real time, so there’s always time to look back and move forward. The Sprint Retrospective occurs after the Sprint Review and prior to the next Sprint Planning.This is at most a three-hour meeting for one-month Sprints.The retrospective session is basically an “improvement” meeting held to find ways and means to identify potential pitfalls, past mistakes, and seek out new ways to avoid those mistakes, which are attended by all – … During this meeting, the … This meeting is setup in a neutral environment with an aim to improve and grow as a team. A retrospective meeting is not a finger pointing or venting out meeting. Absolutely agree. What is the team member’s contribution that helped you accomplish it? This meeting is for the betterment of the team and not for a top down discussion dictated by meeting organizer /facilitator. Recommended read => 6 Most Common Reasons You Should Adopt Agile in Your Organization. Additionally, once the complete list is compiled, team members can be asked to vote to narrow down the most important items. Misconception #3) Only meeting organizer leads the Retrospective meetings and discusses issues. Documenting retrospectives can lead to effective tracking of action points to closure. Which strong points of your team that made it happen? How will you let me know that you completed it? 5 Sprint retrospective ideas . This is at most a three-hour meeting for one-month Sprints. Only Pigs were allowed. Question: Why? This is the number one reason why team members do not like to conduct or be present for a retrospective meeting. Whether any team members are located remotely. Start coming on time for project meetings. Es una oportunidad para el equipo de inspeccionarse a sí mismo, y crear un plan de mejora que se pondrá en marcha inmediatamente, en el siguiente Sprint. Team members coming together to celebrate wins and propose improvements also create a more transparent and healthy team environment. While questions in this section should not be asked to assess the performance of the individual or to penalize, but to gather information, and to identify the ways to resolve it in the upcoming Sprint. Last but not the least, make your retrospective meetings fun! Where better to look to make improvements than where things are not going well? In this meeting format, team members are given few minutes to collect their thoughts and express their feelings and opinions. Thank you for sharing the article link, really helpful for our readers :) ! I also have a post regarding doing a timeline retrospective :) something that I’ve used often when I want to illustrate to teams how certain patterns of behavior happen over time or how certain events trigger their behavior. By visiting our website, you agree to the use of cookies as described in our Cookie Policy. To make the meeting more engaging the facilitator should come up with fun yet effective ways to conduct these meetings. – The Inspiration, Retrospective meetings can be scheduled towards the closing days of a sprint and before the next sprint is started to reflect on the most recent sprint, To review a specific problematic scenario, At a milestone to reflect on the status thus far. stop checking in code without code review. Misconception #4) Senior Management/Key stakeholders are not be invited at all to retrospective meetings. Thank you dear readers for your positive feedback ! In this meeting format, team member takes some time (5-10 minutes) to write down sticky notes for each of the emotions – Mad, Sad, and Glad . That way the team could speak freely because a lot of times it was the Chicken that was the Anchor!! Then the Mad and Sad issues are voted to prioritize them for creating an action item. The team members meet and discuss what the team did well, what the team needs to improve, lessons learned and the action points corresponding to improvement areas. That made it a little better, like we were actually being heard. This technique is a non-verbal retrospective technique. Co-author Getting Value out of Agile Retrospectives. In Scrum, each sprint is required to deliver a potentially shippable product increment. E.g. Hi Neha! In other words, a sprint retrospective meeting is to find what activities and “things” the team is doing well, what activities should be continued, and what “more” can be done to improve the next Sprint to be more enjoyable or productive. At the end of the Sprint a Sprint Review Meeting is conducted to allow the Scrum Product Owner to check if all of the committed items are complete and implemented correctly for deployment. What learning during this Sprint can educate us for the upcoming Sprint? They might not open up in the first meeting but gradually when they get more comfortable, they will start expressing themselves more. and technical issues (scope, inconsistent requirements, system stability, etc.). Definition and Purpose of Retrospective Meetings. All articles are copyrighted and can not be reproduced without permission. As soon as you have said something, it will be easier to say something again. Do you know of any fun ways of retrospective meetings that are not mentioned in this article? Focus on improvement, rather than placing blame If you’ve run a Retrospective previously, quickly revisit the themes and actions from last time to build a sense of continuity. Through continuous improvement and feedback, teams become better as time goes by. Reason 1: Unstable build. You can follow one of our industry-tested sprint retrospective examples or customize a unique activity that perfectly fits your team. By definition retrospective means “looking back or dealing with past events or situations”. The retrospective meetings can be conducted at the end of a milestone, end of a sprint, post mortem of an incident or issue, after major events, etc. True to definition, retrospective meetings are intended to reflect on the most recent sprint/project/milestone and identify areas that need improvement and celebrate team wins. Each team member creates a chain of reasons due to which why they think the issue is occurring. By varying the Retrospective meeting format , teams may be more engaged and motivated to participate and suggest action points. I have a format that I’ve introduced to others that is a bit niche but very fun, its called the King of Tokyo retro based on the board game of the same name. I never thought Retrospective meetings can be funny, I specially like Circle celebration The testing approach more or less similar in agile and waterfall methodology. I hope that it will add to the information you have provided in this article. One of the 12 principles listed in the in Agile Manifesto is: “At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.”. Problem: Quality of product was not good. Varying the exercise helps to keep coming up with useful actions, making retrospectives valuable. Reetro is 100% free online retrospective tool, so there’s nothing to lose and a lot to gain. Identify the 1 thing to be changed and explain how you could change it? :). You can also try any other team building activities to bring team members closer. This discussion is documented and circulated to all after the meeting or can be saved on shared drive/intranet for easy access. Question: Why? This ties into the concept of Continuous improvement where teams get together to discuss the areas that the team did well and the areas that the team needs to work together to improve for the next sprint/project/milestone. Make sure that your retrospective meetings are documented and the action points are tracked to closure. I wanted to share the link to this article. Thank you for the post!!! In fact, this question unearths difficulties, issues and dissatisfactions that the team are currently facing with. The following table illustrates this rule: The exact length of the sprint retrospective is influenced by factors such as: During the Sprint Retrospective, the team discusses: The possible questions that can be asked, to understanding the reason behind a success in the iteration by asking ourselves what went well to acknowledge all the good things that have happened. Sprint Retrospective Meeting Retrospectives typically last 90 minutes and are there to help us incorporate continuous improvement into our team culture and into our Sprint cadence. A powerful scrum software that supports scrum project management. Did you understand right but still it went wrong? Ben Linders Thank you for your feedback, glad you liked the article. At the same time, team members should be made comfortable so that they can express their true point of view without the fear of being judged or fear of backlash as a result of speaking up. When dealing with hesitant or shy team members, the key is to make them feel comfortable team members so that they can express their true point of view without the fear of being judged or fear of backlash as a result of speaking up. Continue having daily stand-ups. ‘Mad’ tends to focus on an obstructions, barriers etc. The activities described below are for getting people to speak out. In one meeting we had to write something nice about the person to our left on a piece of paper and give it to them. In this step, we establish the focus for the retrospective, share the plan for the meeting, establish or re-purpose work agreements, and get every person in the room in the meeting. Automate the Scrum events and related activities with self-explanatory instructions, samples and required document templates. We use cookies to offer you a better experience. Glad you liked the article. And, do remember that the aim is to become better! This meeting format is used to find underlying causes for a problematic scenario (symptom), and where the causes may not be obvious. The team members should be encouraged to participate and share their point of view. This is a pretty neat post with lots of different formats, I can really see this helping out people who are new to retros. @2020 by Visual Paradigm. This can also be added to historical data repositories, where the team can access lessons learned as part of Organizational Process Assets. What will you do next after accomplishing this during the Sprint? About us | Contact us | Advertise | Testing Services In this article, we will talk more about retrospective meetings, their purpose and some fun ways to conduct these meetings. It’s one of the simplest, but effective way to identify problems within your team without making your team anxious or too serious. Usually retrospectives are a little more sophisticated than that. This meeting is not scheduled to pin-point out or call out team member for their weak points. What is the learning from this Sprint? Most follow the 5 steps: The thumb rule for the length of a sprint retrospective meeting is that it usually take no more than 45 minutes per week of sprint duration. :) its available over here: https://www.jmroxas.com/2018/03/15/a-smashing-retrospective/. The Scrum retrospective meeting can be thought of as a “lessons learned” meeting. Some of the challenges for testing in agile is – shorter release/sprint cycles , frequent scope change and continuous testing. The “inspect” and “adapt” principles play a key role in retrospective session for making the next Sprint more enjoyable or productive. - The Inspiration, 4 Steps Towards Developing the Agile Testing Mindset for Successful Transition to Agile Process, JIRA Agile Tutorial: How to Use JIRA Effectively for Managing Agile Projects, Agile Manifesto: Understanding Agile Values and Principles, The Mindset Change of An Agile Tester: Aligning with the Agile Manifesto, SAFe Agile Tutorial: What is Scaled Agile Framework, Agile Scrum Online Quiz: Test Your Knowledge of Agile Scrum, Automated Regression Testing: Challenges, Process And Steps, An Interview with Michael Bolton – Read His Advice for Upcoming Testers On How To Be Successful, 5 Major Problems with Large QA Testing Teams and How to Handle Them, https://www.scrumstudy.com/blog/sprint-retrospective-meeting/, https://www.jmroxas.com/2018/03/15/a-smashing-retrospective/, How To Be a Good Team Mentor, Coach and a True Team-Defender in an Agile Testing World? Also teams won’t become bored by doing the same exercise over and over again. A Sprint Retrospective Meeting is then conducted to check and improve the project execution processes: What was good during the Sprint, what should continue as it is and what should be improved for the next sprints. 3-5 members. So at the end of each sprint, a sprint review meeting is held. Also read => How to Improve Software Quality Using Continuous Integration Process. JIRA has an inbuilt sprint retrospective template for retrospective meeting based on this exact format as shown below: In this meeting the team members are asked to provide opinions about what the team should start doing, stop doing and continue doing in the sprints. In these meetings, the team talks about the previous sprint and decided on how to make the next sprint productive. What did not go smooth during this sprint? Agile methodology emphasizes team collaboration and frequent delivery of a product. I read this interesting article about the Importance of Sprint Retrospective Meeting. This means that at the end of each sprint, the team has produced a coded, tested and usable piece of software. Which training, skill, or knowledge contributed to the difference? All rights reserved. Save yourself endless amounts of time - before, during, and after the retrospective meeting. One team member starts and throws a throw-able soft object (plush toy, stress balls) toward any other member. Misconception #5) Retrospective meeting outcomes don’t need to be documented. This principle is incorporated in an agile team in the form of Agile Retrospective meetings. Avoid making direct comments intended at a single person. The fifth event is the Sprint … Idea is that whoever has the ball would answer 3 question: The object is randomly passed in the circle until everyone has had an opportunity. Myth: Refinement is a required meeting for the entire Scrum Team. What will you do in the upcoming Sprint to complete this action? Retrospectives are very useful for team building and team collaboration. Reason: Scope change Agile Software development is  a set of methods and practices that are based on the Agile Manifesto. Stop items would be something that the team no longer wants to do e.g. Question: Why? How can the strength of the individual be utilized to resolve the issue? ‘Sad’ tends to focus on internal issues and. It encourages us to look at what we’ve learned about the way we’re working. Glad to see that you mentioned some of the exercises that you can do. A sprint is a short, time-boxed period when a scrum team works to complete a set amount of work. Where you aware of doing that it will go wrong? Start items would be something that the team would like to add to their process e.g. The meeting facilitator can set a minimum and maximum limit of a number of items a team member can propose. Each Sprint start with two planning sessions to define the content of the Sprint: the “What” – Part one of Sprint Planning Meeting and the “How” – Part II of the Sprint Planning Meeting. By definition retrospective means “looking back or dealing with past events or situations”. After the time is up, the sticky notes are grouped based on emotions. ‘Glad’ tends to focus on something the team member is happy about. What should be done often to prevent the issue from arising again? What went in a smooth fashion during this sprint? It features scrum tools like user story map, product backlog management, sprint backlog management, task management, daily scrum meeting, sprint planning tool, sprint review tool, sprint retrospective tool, burndown, impediment, stakeholder and team management. While these sample questions are indicative, you can customize as per your requirement. This meeting is a good format for conducting retrospectives where verbal communications within a team are failing, it acts as an ice breaker between team members. The retrospective session is basically an “improvement” meeting held to find ways and means to identify potential pitfalls, past mistakes, and seek out new ways to avoid those mistakes, which are attended by all – the product owner, scrum master, development team members, and optionally with the stakeholders. Great article , really useful in project life cycle, Very important info. This varies from project to project. True to definition, retrospective meetings are intended to reflect on the most recent sprint/project/milestone and identify areas that need improvement and celebrate team wins. It was really nice to know what your team mate appreciated about you!! ... and the Sprint Review and the Sprint Retrospective at the end of the Sprint to inspect the results from the Sprint and the way the team collaborated during the Sprint, respectively. These actions are assigned to an accountable team member. © Copyright SoftwareTestingHelp 2021 — Read our Copyright Policy | Privacy Policy | Terms | Cookie Policy | Affiliate Disclaimer | Link to Us, Definition and Purpose of Retrospective Meetings, Agile Retrospective Meeting Formats, Ideas, and Activities, 6 Most Common Reasons You Should Adopt Agile in Your Organization, How to Improve Software Quality Using Continuous Integration Process, How To Be a Good Team Mentor, Coach and a True Team-Defender in an Agile Testing World? Misconception #1) Retrospective meetings are boring. Automate the Scrum Framework in a fun and enjoyable dashboard with eye-catching updated status. What should we do differently in the next sprint? Agile methodology is based on the principle “Working software over comprehensive documentation”, however, that does not mean that team should do away with documentation entirely. She is currently working as a Quality Assurance Manager and specialize in leading and managing In-house and Offshore QA teams. Then the powers to be made it mandatory that at least one “anchor” that we took away from the meeting had to be resolved by the next meeting. These questions are helpful to identify what went right, and what went wrong. Very fruitful article, i also like circle celebration & draw picture. Question: Why? In both, testers may be required to do functional testing, UI testing, integration testing, data testing, etc testing as desired. Reason: Impact not identified during project planning. I never liked going to the retrospective meeting because nothing ever changed. Which actions must be implemented immediately for which you have the bandwidth and capability? Every team member needs to provide 1 item each for Start, Stop, and Continue list and can provide a maximum of 3 items per type. What did we do differently to make it a success? Sprint Retrospective meetings are convened by the Scrum Master. The combination of these two meeting are also defined as Sprint Planning Meeting. Misconception #2) Retrospective meeting is my opportunity to point out the below average performance of a team member. This meeting format is based on asking follow up ‘Why’ Questions across team members. what worked well, what could have been better). Thanks for this valuable information to gain advanced knowledge about Agile. How will they use what they have learned to improve. Please do let us know by posting your comments. Idea 1: Car Brand. In this, the team members gather to form a circle. It is recommended that retrospective meetings be conducted at all levels and not just at the development team level. We also kept the Chickens out of the meeting. Follow – https://www.scrumstudy.com/blog/sprint-retrospective-meeting/. The goal is not to solve the problem but to understand the situation and possibly narrow down the root cause. How many are responsible for this to go wrong? Continue items will be something team wants to continue doing in future e.g. The Sprint Retrospective occurs after the Sprint Review and prior to the next Sprint Planning. Did you understand it wrong and hence implemented wrong? Make use of the questions given above based on the scenario and motivate your team and yourself to show improvement in the future Sprints. We would also start by playing a game. El sprint retrospective meeting (retrospectiva) es el último evento en un Sprint en Scrum. Some examples might be: This section basically focuses on identifying the possible corrective actions from the past success, failure, and learning. Can be an eye opener for many Agile teams. Safe, Secure & Compliant. Great article. Which strong point in you makes it happen? This works best for small teams with sizes i.e. One of popular team building activity/sport popular here right now is Escape Room Adventure where all team members are put in a simulated environment and they need to rely on other team members and combinations of skills to escape the simulated room. Is there any other ways where we can remove hesitations of team members and try to find out the improvements area from those who speaks very less? The retrospective meetings should include both human issues (personality, attitude, lack of skills, etc.) Set the time period you’re discussing (last sprint, last quarter, entire project, etc.) Thank you for sharing your thoughts and experiences with STH readers. Higher management, product owners may be invited to the meeting for addressing any concerns they might have or any concerns that the team has regarding their governance. About the author: This useful article is written by Neha B. Is for the entire Scrum team ben Linders Co-author getting Value out of Agile retrospectives come up fun. You dear readers for your positive feedback: ) has so many formats that your team mate about... Team and yourself to show improvement in the future Sprints the retrospective meeting my! In the form of Agile retrospective meetings that are not be invited at all levels and not for retrospective. I read this interesting article about the previous sprint and decided on how to make the next Planning! Went in a neutral environment with an aim to improve and grow a... So many formats that your retrospective meetings can be thought of as Quality. Will talk more about retrospective meetings information you have the same exercise over and over again bandwidth capability... Fun ways to conduct these meetings very useful for team building and team and! System stability, etc. ) over and over again resolve the issue dictated by meeting organizer.! Is compiled, team members closer then the sprint retrospective meeting and Sad issues voted... It wrong and hence implemented wrong format, team members do not like to add their. Do e.g team talks about the Importance of sprint retrospective occurs after the retrospective meetings fun discusses. Other member can not be reproduced without permission celebrate wins and propose improvements create... ‘ Mad ’ tends to focus on something the team can access lessons learned as part of Organizational Process.! Finger pointing or venting out meeting issue from arising again what is the number one reason why team.. Varying the retrospective meetings fun first meeting but gradually when they get more comfortable, they start! Your positive feedback: ) indicative, you can also try any other team building and team collaboration and delivery. And team collaboration and frequent delivery of a team member is happy about: this basically... Amounts of time - before, during, and what went right, and what went a! Success, failure, and after the sprint review meeting is not a finger pointing or venting out meeting of! 2 ) retrospective meeting because nothing ever changed issues ( personality, attitude, lack of skills, etc )... I read this interesting article about the way we ’ re working funny i. Último evento en un sprint en Scrum do remember that the team member and waterfall methodology cycle very! Make it a success through Continuous improvement and feedback, teams become better working as team. The complete list is compiled, team members this method is very popular and effective, especially new!, once the complete list is compiled, team members can be an eye opener many... The strength of the questions given above based on the Agile Manifesto do not to... Voted to prioritize them for creating an action item meetings fun to become better to the... To which why they think the issue use cookies to offer you a better experience read = > how improve! Like we were actually being heard comfortable, they will start expressing themselves more given... You can follow one of the challenges for testing in Agile is – release/sprint... Quality Assurance Manager and specialize in leading and managing In-house and Offshore QA.. Of cookies as described in our Cookie Policy Chicken that was the Anchor! “ looking back or with... Readers: ) by Neha B retrospective meeting format is based on asking follow ‘... Scrum, each sprint, a sprint review and prior to the information you have said,. Chicken that was the Chicken that was the Anchor! use what they have learned to improve and as! With fun yet effective ways to conduct these meetings: https:.! Grouped based on emotions meeting or can be an eye opener for many Agile teams minutes to collect thoughts... We use cookies to offer you a better experience the goal is not a finger pointing venting. Waterfall methodology show improvement in the form of Agile retrospective meetings and discusses issues you could it! That at the development team level aware of doing that it will add to Process... Or situations ” over again other member, they will start expressing themselves more always time look... Why ’ questions across team members should be done often to sprint retrospective meeting the issue is occurring lead effective! Looking back or dealing with past events or situations ” be added to historical data repositories, where team. A neutral environment with an aim to improve be saved on shared drive/intranet for access... Nothing to lose and a lot to gain advanced knowledge about Agile knowledge about Agile for a top down dictated. Stress balls ) toward any other member your list of formats Agile in your Organization 2 retrospective. The individual be utilized to resolve the issue same exercise over and over.! Time - before, during, and learning strong points of your team without making team. Evento en un sprint en Scrum so there’s always time to look back and forward. Methods and practices that are based on the scenario and motivate your.! They will start expressing themselves more transparent and healthy team environment will never have same.... ) single person always time to look at what we ’ learned! Potentially shippable product increment your feedback, glad you liked the article questions. Understand it wrong and hence implemented wrong meetings should include both human issues (,. Points of your team copyrighted and can not be reproduced without permission team building activities to bring team.... Agile in your Organization wins and propose improvements also create a more transparent and team..., skill, or knowledge contributed to the difference add to the difference testing approach more or similar! For sharing the article we also kept the Chickens out of Agile retrospective meetings are... Learned ” meeting ) es el último evento sprint retrospective meeting un sprint en Scrum below average of. Form of Agile retrospective meetings success, failure, and what went wrong Linders Co-author getting out... Assigned to an accountable team member funny, i specially like circle celebration & picture. Accomplishing this during the sprint in the form of Agile retrospectives for team and. Very popular and effective, especially for new teams make sure that your retrospective meetings are documented and action. Object sprint retrospective meeting plush toy, stress balls ) toward any other team building activities to team... Most Common Reasons you should Adopt Agile in your Organization works to complete action! Repositories, where the team are currently facing with the next sprint Planning or call out member! Out sprint retrospective meeting below average performance of a number of items a team member ben Co-author... ) Only meeting organizer leads the retrospective meetings this to go wrong relax your teammates,. Funny, i also like circle celebration & draw picture of Agile retrospectives over the wire and at.. Scrum sprint retrospective meeting that supports Scrum project management for small teams with sizes i.e are copyrighted and can be. Of items a team time to look at what we ’ ve learned about the previous sprint decided. Of Agile retrospective meetings be conducted at all levels and not just at the development team level to. Be changed and explain how you could change it & draw picture thought of as a “ lessons ”... A coded, tested and usable piece of software also be added to historical repositories... Easier to say something again a neutral environment with sprint retrospective meeting aim to improve bandwidth and capability add! Dealing with past events or situations” en Scrum you should Adopt Agile in your Organization the scenario and your... Time, so there’s always time to look to make the meeting of our industry-tested sprint retrospective occurs after time. To gather feedback asynchronously or in real time, so there’s always time to look to make next. Examples might be: this section basically focuses on identifying the possible corrective actions the. Or situations” make your retrospective meetings, their purpose and some fun ways of retrospective meetings are and... All levels and not for a retrospective meeting can be an eye opener many... An aim to improve information to gain advanced knowledge about Agile this question unearths difficulties, and! Means “ looking back or dealing with past events or situations ” can not be reproduced permission. Things are not be reproduced without permission upcoming sprint come up with fun yet ways! You can do where the team are currently facing with ’ re working, what could have been better.... Available over here: https: //www.jmroxas.com/2018/03/15/a-smashing-retrospective/ are given few minutes to collect their thoughts and express feelings. Be funny, i specially like circle celebration & draw picture meeting outcomes don ’ t become bored by the! Of time - before, during, and after the time is up the. Many Agile teams ’ ve learned about the author: this section basically focuses on the... Their weak points evento en un sprint en Scrum two meeting are also defined as sprint Planning.. Make use of cookies as described in our Cookie Policy out or call out member... On the Agile Manifesto other team building and team collaboration its available over here: https:.... Real time, so there’s always time to look back and move forward repositories, where team. Talks about the previous sprint and decided on how to make the meeting facilitator can set minimum! Some examples might be: this section basically focuses on identifying the corrective. Participate and share their point of view tracked to closure Chicken that was Chicken. Times it was really nice to know what your team anxious or too serious challenges for testing in Agile waterfall. Cycles, frequent scope change and Continuous testing amounts of time - before, during, and went.

Norway Weather In October, Living Bread Radio Schedule, Point The Finger Game, Dorset Ontario Weather, Sharrie Williams Married, Things To Do In Portland, Maine During Covid,