Share this
by Luis Gonçalves on May 1, 2024 3:05:59 AM
Welcome to our latest blog post, where we delve into the world of Agile Retrospectives.
Over the years, I've experimented with numerous retrospective exercises and have seen first-hand how they can transform team dynamics and boost productivity.
In this post, I'm excited to share a curated collection of these ideas, each tested and refined through practical application. If you've developed any retrospective exercises or have favourites that you swear by, I would love to hear from you!
Feel free to reach out, and perhaps your exercise could be featured in our next guest blog. Let's explore these insights together and enhance our Agile practices.
Agile Retrospectives Ideas
Express Your Team´s Feelings in a Team Retrospective
"Express Yourself" is an agile retrospective exercise designed to help team members articulate and visualize their feelings about specific topics in a safe, structured environment. This activity is especially useful in teams with new members, shy individuals, or dominant personalities, as it encourages everyone to participate equally. By using a simple method of placing post-it notes along an emotional spectrum—from happy to sad—participants can express their feelings without the pressure of verbalizing them directly.
The exercise begins with a brief setup, followed by a period of silent reflection where team members write down a single word that describes their feelings on a post-it note. They then place this note on a prepared scale that visually represents the emotional range of the team. This is followed by a short discussion, limited to 6-8 minutes, where each participant can elaborate on their feelings if they choose. The Scrum Master facilitates this process, ensuring that the focus remains on expressing and understanding emotions rather than solving any issues raised during the exercise.
This technique not only helps in quickly gauging the mood and concerns of the team as they enter a retrospective session but also sets the stage for more in-depth discussions. It acts as a warm-up that encourages openness and builds the groundwork for effective communication throughout the session. The Scrum Master plays a crucial role in keeping the discussion brief and focused, preventing it from veering into solution-finding too early, which is reserved for later parts of the retrospective.
2 Truths and a Lie Retrospective
"Two Truths and a Lie" is a dynamic retrospective activity adapted from a classic icebreaker game to enhance engagement and teamwork in groups that are familiar with each other but may be experiencing a lull in collaboration due to repetitive retrospective exercises. In this activity, each team member prepares three statements about the past sprint: two that are true and one that is a lie, relating to their personal experiences, skills, or observations. This setup not only stimulates team interaction but also fosters a fun environment where members can challenge each other's assertions and guess the inaccuracies.
The game is structured into three main phases: setting up, playing, and wrapping up. Initially, team members write their statements on post-its during a brief setup period, and then take turns presenting them to the group. As each member shares, the rest of the team discusses and votes on which statement they believe is the lie. This encourages active participation and critical thinking. The session concludes with a discussion where all truths and identified lies with negative connotations are analyzed to derive actionable insights for team improvement and future focus areas, further adding to the retrospective's productivity.
Offering a variation like "Two Truths and a Wish" can also help teams that find it challenging to fabricate lies. In this alternative, the third statement is a wish—something a team member hopes for—adding a layer of aspiration to the exercise. This retrospective is not only effective across various team maturity levels but also versatile in adapting to the team's needs, making it an invaluable tool for enhancing team dynamics and identifying practical solutions for continuous improvement.
Starfish
The Starfish Exercise, detailed in the book "Getting Value out of Agile Retrospectives" co-authored by myself and Ben Linders, is an innovative retrospective tool designed to enhance team reflection and improvement. This method expands upon the traditional retrospective questions—what went well, what did not, and what should be improved—by categorizing team activities into five areas: Stop, Less, Keep, More, and Start. These categories help teams clearly identify practices that are either wasteful or valuable, and those that should be increased or introduced. The exercise encourages teams to critically evaluate their work processes and behaviours to foster a more productive and insightful discussion on team dynamics and efficiency.
The Starfish Exercise is versatile and straightforward, making it suitable for any team regardless of maturity or specific circumstances. It does not require teams to be co-located; digital tools like Lino can facilitate the exercise remotely. The process involves drawing a starfish diagram on a flip chart, brainstorming, and discussing ideas in each of the five categories, with a structured approach to prioritizing and implementing changes. This method typically starts with addressing negative aspects and progressively moves towards positive actions, helping teams conclude the retrospective on an uplifting note.
This retrospective technique is particularly useful in iterations where teams have experienced significant highs and lows, providing a comprehensive overview of successes and areas for improvement. By structuring the session to end with actionable items and a positive outlook, teams can leave feeling motivated and clear about their future direction. This feedback-driven approach not only enhances team collaboration but also ensures continuous improvement.
Return of Time Invested
The Agile Retrospective Return of Time Invested (ROTI) exercise, adapted from a standard ROI approach found in Diana and Esther’s Agile Retrospectives book, has significantly improved the quality of feedback in my sessions. This method goes beyond typical quantitative evaluations that use a simple numerical scale, offering a way to capture both qualitative and quantitative feedback effectively. Unlike standard rating systems that provide limited insights into what actually worked well or poorly, the ROTI exercise allows participants to articulate specific reasons behind their ratings. This dual feedback mechanism is invaluable in understanding the strengths and weaknesses of a session and can significantly enhance future retrospectives.
I frequently use this exercise at the end of Agile Retrospectives to gather comprehensive feedback, especially when leading sessions with introverted teams. Many facilitators struggle to elicit spoken feedback from such groups, but I’ve found that asking participants to write down their thoughts leads to more creative and honest responses. This method involves using a flipchart divided into quadrants labelled with axes for 'Value' and 'Fun', ranging from "Boring/No Value" to "A Lot of Fun/Great Value". Participants place their feedback on this chart, providing insights into what they found valuable or enjoyable about the session.
To conduct this exercise, simply prepare a flipchart with the two axes and the four quadrants, provide post-its and markers to the team members, and allow them time to consider and document their feedback. This not only helps in capturing tangible reasons behind their evaluations but also makes it easier to tailor future sessions based on precise participant feedback, thereby improving the effectiveness of your retrospectives over time. This approach is particularly beneficial as it respects the communication styles of all participants, fostering a more inclusive and productive feedback environment.
Appreciation
In a recent blog update, I shared a new Agile Retrospective exercise that I picked up during a Team Coaching training in Amsterdam. This exercise is designed to end an Agile Retrospective on a positive note by fostering an appreciation culture within teams. Appreciation practices are well-documented for their ability to enhance team performance and create a positive work environment. This particular exercise involves a simple setup where team members take turns sitting in a 'Central Chair' and receiving appreciative feedback from their colleagues, which can significantly boost team morale and cohesion.
The structure of the exercise is straightforward: arrange chairs in a semi-circle with one central chair facing the group. Each team member takes a turn in the central chair, during which the others offer specific appreciation for that person's contributions. This process not only reinforces positive behavior but also helps team members recognize and verbalize the value each person brings to the team. It's a powerful tool for building a culture of appreciation and can be integrated into any meeting, not just retrospectives, to maintain ongoing positive dynamics.
Implementing this exercise doesn't require any special occasion. I advocate for its use in various settings as a means to continually nurture and strengthen team bonds. By starting or ending meetings with a round of appreciation, teams can cultivate an environment of respect and deep listening, which are crucial for effective collaboration and team growth. This approach ensures that everyone gets a chance to both give and receive positive feedback, enhancing the overall team spirit and engagement.
In a recent blog post, I introduced the concept of using kudo cards in Agile Retrospectives, a simple yet powerful tool to foster appreciation within teams. Although the idea of kudo cards is not entirely new, it is underutilized in many organizational settings. Kudo cards serve as personal tokens of appreciation that team members can give one another to acknowledge good behaviour or valuable contributions. This method contrasts with traditional monetary rewards and is supported by thought leaders like Jurgen Appelo, who advocate for more meaningful recognition practices.
The beauty of kudo cards lies in their flexibility and simplicity. They can be used at any point during a retrospective—either to kick off the session on a positive note or to wrap up with a sense of accomplishment and mutual respect. Teams can choose to use these cards in sprints where the outcomes have been exceptionally good to boost morale, or even in challenging sprints to highlight the positives and maintain team spirit. This ongoing practice of giving and receiving kudo cards can significantly enhance team dynamics and foster a culture of appreciation and acknowledgement.
Implementing kudo cards is straightforward: at the beginning or end of a retrospective, team members write appreciations on cards for their colleagues, thanking them for specific actions or support during the sprint. These cards can either be handmade or purchased, such as those designed by Jurgen Appelo available on Amazon. Once filled out, the cards can be displayed on an 'Appreciation Wall,' serving as a constant visual reminder of the team’s collaborative spirit and positive interactions. This practice not only strengthens team bonds but also encourages a continuous flow of positive feedback among team members.
Lego Retrospective
The LEGO Retrospective is an engaging and creative exercise used in Agile Retrospectives that allows team members to express their thoughts and ideas through the construction of LEGO® models. This method taps into the playful childhood memories of LEGO® to motivate participation, making it especially effective for teams including introverted members who may be less inclined to vocalize their thoughts in traditional settings. By constructing physical representations of their reflections on past sprints and future goals, team members can abstractly and visually communicate their insights, which can help to foster a more open and understanding team environment.
This exercise is particularly useful for new facilitators as it provides a structured yet flexible approach to guiding retrospectives. To implement it, ensure a comfortable and altered space that doesn't feel like the usual work environment, perhaps enhanced with background music to set a relaxed tone. Start by having team members build a LEGO® figure representing the last sprint, followed by a model depicting the next steps or improvements for the team. These activities not only stimulate creative thinking but also encourage a deep dive into constructive discussions about the team's dynamics and processes.
The session concludes by discussing the models and summarizing the insights on Post-Its that are displayed on a wall. This visual and physical representation of feedback helps in prioritizing actions through methods such as dot-voting, ensuring that the team leaves the retrospective with clear, actionable goals. The LEGO Retrospective thus serves as a powerful tool to break down communication barriers and enhance collaborative problem-solving within Agile teams.
Sailboat
The Sailboat Exercise, often utilized in Agile Retrospectives, is a simple and visual technique that helps teams articulate their goals, identify potential risks, and determine factors that could impede or accelerate their progress. Described in the book Getting Value out of Agile Retrospectives, this exercise encourages teams to envision their journey towards achieving their objectives, making it particularly useful for teams with dependencies on one another or when conducting retrospectives that involve multiple teams. By drawing a sailboat, islands, rocks, and various weather conditions on a flip chart, teams metaphorically explore their path forward, discussing and strategizing around the visual elements that represent different aspects of their work environment.
To conduct the exercise, the facilitator sketches a sailboat (representing the team), islands (goals), rocks (risks), and other symbols like clouds and wind (aiding factors) on a board. Team members then brainstorm and plot ideas on these elements, identifying what propels the team forward and what might be holding them back. This setup not only fosters a creative discussion about ongoing projects but also visually captures the dynamics of teamwork and project management. The session progresses with team members discussing how to continue leveraging positive influences (clouds/wind) and how to mitigate identified risks (rocks), concluding with prioritizing and planning actions to address the most critical challenges.
Overall, the Sailboat Exercise is effective for team alignment on objectives and challenges, offering a clear, structured way for team members to express concerns and contributions towards collective goals. This can be adapted for teams that are not collocated by using online collaborative tools to simulate the interactive and visual aspects of the exercise, ensuring all team members can participate fully regardless of their physical location.
The "High-Performance Tree" exercise, as described by Lyssa Adkins in her book "Coaching Agile Teams," serves as a powerful metaphorical tool for helping agile teams define and realize their vision towards becoming high-performing. This exercise employs the imagery of a tree, where the roots represent the five Scrum values: Commitment, Courage, Openness, Focus, and Respect. These values are essential for building a strong foundation that enables a team to grow and achieve remarkable results. The exercise is designed to make team members reflect on these values deeply, ensuring they understand and adhere to them, thereby fostering an environment conducive to high performance.
This technique can be adapted to teams at different maturity levels and is particularly beneficial at various stages such as team formation, addressing ongoing challenges, or when a team is transitioning to higher levels of performance. During the exercise, the coach draws a tree and labels each root with one of the Scrum values, discussing their significance and how they contribute to team dynamics and success. Subsequently, characteristics of high-performing teams, such as empowerment and self-organization, are added to the branches, helping teams visualize their growth path and identify areas for improvement.
Overall, the High-Performance Tree is not just an exercise but a continual reference point for teams aiming to excel. It helps in setting clear expectations, provides a visual reminder of the team’s goals, and is a creative way to engage team members in a discussion about what it truly means to be a part of a vibrant and effective agile team. This exercise can be effectively conducted in-person or virtually, making it a versatile tool in the arsenal of agile coaches and Scrum Masters looking to elevate their teams' performance.
Car Brand
Starting an effective Agile Retrospective can be challenging, especially when team members are new to each other or hesitant to openly share their thoughts and feelings. The "Car Brand" exercise, described in the blog post, serves as an engaging opener to help set the stage for a retrospective. This technique allows participants to metaphorically express their views on the sprint's performance by associating it with a brand of car. For instance, a highly successful sprint might be likened to a Ferrari, while a sprint with ups and downs could be compared to a Fiat. This not only makes it easier for team members to share their perceptions without direct criticism but also helps to quickly gauge the overall team sentiment.
The exercise is simple to implement: the facilitator asks each team member to think of a car brand that they feel represents the past sprint and then share their choice without providing justifications initially. This preliminary round is crucial as it gives everyone an initial idea of team perspectives. Following this, participants are encouraged to think about their "dream car" – a metaphor for what they would want in an ideal sprint. They then brainstormed changes that could transform the next sprint into this "dream car" scenario, discussing and prioritizing these ideas to identify key areas for improvement.
Overall, the Car Brand exercise is versatile and can be adapted to various team settings, including those that are not collocated, using virtual tools to facilitate discussion. This opener not only warms up the team for more detailed discussions but also fosters a creative and open environment that encourages collective problem-solving and alignment on goals and expectations.
Constellation
Starting an effective retrospective in Scrum involves engaging team members right from the outset with a compelling opener. This post delves into the "Constellation" exercise, a method described in the book "Getting Value out of Agile Retrospectives." The Constellation exercise is particularly useful for teams where members may be reticent about sharing opinions or feelings openly, especially in the early stages of team formation or when there is a lack of trust. It allows participants to express their level of agreement or disagreement with statements silently by positioning themselves closer or farther from a central object, labelled as the "centre of the Universe." This non-verbal method of expression helps reveal the collective team's perspectives without initiating early discussions, making it an excellent technique for understanding team alignment on various issues.
The exercise is simple and adaptable, making it suitable for any retrospective regardless of the specific occasion. It works particularly well in situations where there might be differing opinions on team practices and a need to align everyone's understanding without confrontation. To implement it, the facilitator creates an open space and reads out statements related to key aspects of the team’s work, like the maturity of their continuous integration process. Team members move in relation to the centre based on how much they agree or disagree with each statement. Observing the team's positioning relative to each statement allows everyone to visually gauge overall sentiments and areas of discord or consensus.
Overall, the Constellation exercise serves as an effective and engaging opener for retrospectives, providing clear insights into team dynamics and areas that may require attention or further discussion. It helps set the stage for a more detailed retrospective by breaking down barriers to honest communication and setting a collaborative tone for the session. Whether conducted in-person or virtually, this exercise can significantly enhance the productivity and effectiveness of retrospective meetings.
Team Assessment Survey
In this post, I introduce the Team Assessment Survey as an effective tool for conducting retrospectives within the SAFe framework. Adapted from Dean Leffingwell's original assessment, this exercise is featured in the book "Getting Value out of Agile Retrospectives," which I co-authored with Ben Linders. The survey aims to evaluate team performance across four main areas: Product Ownership Health, Sprint Health, Team Health, and Technical Health. By rating various aspects of these areas on a scale from zero to five, teams can visually identify which areas need more attention and strategize on improvements for future sprints.
The Team Assessment Survey is straightforward to administer using an Excel sheet and does not require any special occasion, making it versatile for regular use. It allows teams to reflect not only on what went wrong during a sprint but also to uncover underlying issues that might be causing these problems, such as gaps in unit testing or automation practices. After filling out the survey, teams can generate graphical representations of their scores to facilitate discussion and decision-making on areas for improvement. This visual feedback helps teams prioritize their actions and focus on one key area at a time for enhancement.
Overall, the Team Assessment Survey is a valuable tool for agile teams seeking to improve their processes and outcomes systematically. It supports teams in identifying both strengths and weaknesses in a structured manner, enabling focused discussions and targeted improvements. This exercise can be effectively implemented in both collocated and virtual team setups, making it a flexible option for diverse team configurations.
Value Stream Mapping is an effective tool traditionally used in manufacturing but equally applicable in software development and other industries to enhance retrospective exercises. This technique, detailed in the book "Getting Value out of Agile Retrospectives," helps teams visualize their workflow processes to identify inefficiencies and areas for improvement. By mapping out each step of a product or service's lifecycle from inception to delivery, teams can see where delays occur, where processes can be optimized, and how effectively they are delivering value to the customer. This exercise provides a wealth of data that can be instrumental in diagnosing issues such as bottlenecks, dependencies, and blockers within the development process, thus facilitating targeted and impactful improvements.
Although Value Stream Mapping is beneficial, it is particularly advantageous for mature teams that are well-versed in agile methodologies. Less experienced teams might struggle to interpret and act on the complex issues this exercise tends to reveal, such as the nuances of QA and documentation processes. For teams that are ready, this technique can illuminate critical insights into reducing inefficiencies like extensive QA tails through approaches like TDD, ATDD, and continuous integration within the sprint.
Implementing Value Stream Mapping involves continuous tracking throughout the iteration rather than being a one-off retrospective activity. Teams use a visual representation, often on flip-chart paper or digitally via tools like Excel, to mark activities that add value above a baseline and non-value-adding tasks below it. This ongoing documentation helps teams identify wasteful practices and streamline processes. As a result, teams can discuss these findings during their retrospectives to make informed decisions about future improvements, making Value Stream Mapping a powerful tool for enhancing team performance and product quality.
Happiness Index
The Happiness Index is an insightful exercise from the book "Getting Value out of Agile Retrospectives," designed to chart the emotional highs and lows of team members throughout a sprint. This graphical representation connects team members' feelings to specific sprint events, helping identify factors that impact team performance. For instance, recurring issues like build server problems could be visually linked to dips in team morale. Such visualization aids in understanding the emotional undercurrents of the team, which can be crucial for addressing both technical and interpersonal challenges that affect productivity.
Implementing the Happiness Index can be done in two main ways: either retrospectively at the end of the sprint or progressively each day. In the retrospective approach, team members work in small groups to recall and plot significant events and their emotional responses during the sprint. This collective mapping can then be synthesized into a comprehensive team graph, providing a holistic view of the sprint’s emotional trajectory. Alternatively, individuals can record their daily emotional states throughout the sprint, ensuring a more continuous and detailed emotional record that might capture nuances sometimes lost in retrospective recollections.
Both methods of the Happiness Index exercise offer valuable insights into the team's dynamics and can help facilitate more effective discussions on improving the work environment and processes. By pinpointing specific events that trigger positive or negative emotional responses, teams can strategize on reinforcing positive influencers and mitigating stressors. This exercise is adaptable to both collocated and remote teams, making it a versatile tool for Agile coaches and facilitators aiming to enhance team harmony and efficiency.
The Instant Retrospective is a dynamic exercise designed for agile teams to address and resolve issues promptly, rather than waiting for scheduled retrospectives. This approach is particularly beneficial for tackling critical issues that impact team performance, ensuring that problems are resolved without unnecessary delays. Unlike traditional retrospectives that review general team and process performance at the end of an iteration, the Instant Retrospective focuses on immediate problem-solving. It empowers teams to initiate discussions about specific issues as they arise, promoting a culture of quick response and continuous dialogue, which is essential for maintaining momentum and achieving team objectives.
This technique can be used at any point when an issue is too urgent to hold off until the next scheduled retrospective. The process involves a focused discussion on a single topic, allowing for a thorough analysis and understanding of the issue at hand. Teams gather to brainstorm potential solutions, ensuring that each member has the opportunity to contribute. This collaborative problem-solving session not only enhances team engagement but also ensures that solutions are collectively owned and more likely to be implemented effectively. The facilitator plays a crucial role in guiding the discussion, keeping it within a strict timeframe (typically 30-45 minutes), and helping the team prioritize and visualize action points on a flipchart to ensure visibility and accountability.
Overall, the Instant Retrospective is an effective tool for agile teams that need to address specific problems quickly and efficiently. It reinforces the agile principles of adaptability and continuous improvement, allowing teams to react to challenges proactively and maintain high performance. By enabling teams to deal with issues as they occur, the Instant Retrospective ensures that the agile process is not just a routine, but a dynamic framework that truly supports the team's needs.
DAKI Retrospective
The DAKI (Drop, Add, Keep, Improve) exercise is a structured approach used during agile retrospectives to help teams evaluate and refine their processes. This method facilitates targeted discussions on aspects of the team's workflow that need adjustment, ensuring continuous improvement. Specifically, DAKI allows team members to identify what they would like to drop (e.g., unnecessary meetings that may involve micromanagement), add (e.g., weekly breakfasts to foster camaraderie), keep (e.g., motivational elements like music during stand-ups), and improve (e.g., strategies to reduce technical debt). This exercise is particularly effective after several sprints with the same team, as it builds on the team's shared experiences to propose meaningful changes.
To implement the DAKI exercise in a retrospective, the facilitator should prepare a four-cell chart representing each component of DAKI and allocate about 30 minutes for the session. The facilitator introduces the exercise with clear, neutral examples to ensure a non-confrontational environment. The team then collaboratively fills out each section—discussing what to drop, add, keep, and improve. This not only helps in pinpointing specific action items but also engages the team in collective decision-making. For instance, improvements identified can be transformed into actionable items, such as simplifying user stories or scheduling strategic meetings with stakeholders to address issues like micromanagement. By regularly reflecting and adjusting through exercises like DAKI, agile teams can significantly enhance their effectiveness and cohesion
Energizing Retrospective
The Energizing Retrospective is a dynamic exercise designed to invigorate teams and enhance their retrospective sessions, making them more engaging and productive. This exercise, as used by Sam and Karen from Growing Agile, includes several phases structured to maximize team involvement and ensure actionable outcomes. It begins with a check-in phase where each team member uses sticky notes under headings like "Be Brave" and "Be Amazing" to express their thoughts about the past sprint. This not only encourages personal expression but also sets a positive tone for the session.
The exercise progresses through stages of gathering data, where team members rate the sprint on a scale of 1-10 and list three things that could have improved their experience. This leads to a deeper discussion during the 'Generate Insights' phase, where the team analyzes what was lacking and explores potential improvements. The session culminates in the 'Decide What to Do' phase, where each person champions an action they feel passionate about, leading to a collective decision-making process through dot voting. This structured approach not only pinpoints specific actions but also breaks them down into immediate tasks, fostering a sense of urgency and capability within the team.
Overall, the Energizing Retrospective is structured to transition from reflection to action smoothly, ensuring that each retrospective leaves the team not only energized but also equipped with clear, actionable steps that they can implement immediately. This method is an excellent way for teams to maintain momentum and continuously improve their processes and interactions.
The World Cafe - Agile Retrospective technique
The World Cafe is a dynamic format often used in larger group discussions and can be adapted effectively for Agile Retrospectives, especially in settings involving multiple Scrum teams. This format facilitates extensive sharing and discussion of Scrum practices, patterns, and experiences across different teams, making it particularly valuable for organizations looking to enhance Scrum adoption comprehensively. During a World Cafe retrospective, participants gather at round tables equipped with large sheets of paper and colorful markers, which encourages a free flow of ideas without the conventional constraints of standard retrospectives. This setup is designed to boost creativity and engagement, helping Scrum Masters gain a clearer understanding of the team's progress and challenges in implementing Scrum.
To conduct a World Cafe, participants are divided into small groups of six to ten at each table, with a designated moderator to guide discussions. The process involves three rounds of discussion, with each focusing on a different question that prompts participants to explore various aspects of their Scrum practices. After discussing a question, participants rotate to different tables, bringing new insights and perspectives to each group. This rotation not only helps in spreading ideas but also in addressing common challenges and sharing successful strategies. The outcome of these discussions is then summarized by the moderators, providing valuable insights into the collective experience of the teams.
In summary, the World Cafe model for Agile Retrospectives is an excellent tool for larger groups to collaboratively evaluate their Scrum processes and discover actionable improvements. It encourages a broad exchange of ideas and fosters a sense of community among participants, making it a suitable choice for organizations aiming to deepen their Scrum practice across multiple teams. This method not only helps identify immediate actionable items but also strengthens the overall Scrum framework within the organization.
Did you like this article?
We enable leaders to become highly valued and recognized to make an impact on the World by helping them to design Digital Product Companies that will thrive and nourish in the Digital Age, we do this by applying our own ADAPT Methodology®.
If you want to know how we can help you to start your transformation please check out our: Training.
If you are interested in doing a transformation in your company please check out our: Consulting.
Share this
Organisational Mastery
Get your free copy
ADAPT
Get your free copy
Product First
Get your free copy