Agile Coaches' Corner

Today’s guest is Betty Pierce, a Senior UI/UX Developer at AgileThought. Betty has extensive skills in various front-end frameworks and libraries including React Native, React, and AngularJS. She is also the Director of Women Who Code Tampa and Trainer for GDI Tampa Bay. Her main passion is building front-end architectures for enterprise apps.   In this episode, Betty gives her perspective on the coding groups for women; the women’s groups she is a part of; how she, as an organizer, makes these groups accessible and welcoming for new members; how she runs the groups and participates in them; and how to get involved in these women-oriented groups yourself. She also gives her tips on how to get started and break into the industry as a woman!   Key Takeaways About the groups Betty helps run and their benefits: Helps women stay in the technology profession (especially in the software and development field) Nice to have other women to relate to in a field mostly dominated by men As an organizer, how did Betty make these groups welcoming for new members? She picked an accessible, central location All events are free Offers a lot of introductory classes and meet-ups Always encourages members to join in and not be intimidated Betty’s tips for getting started and breaking into this industry as a woman: Get uncomfortable and try new things Your approach and outlook with problem-solving may be different as a woman so don’t be afraid to speak up Go back to basics (composition 101) when presenting a topic Immerse yourself in events and local meetup groups (such as a Hackathon or one of Betty’s groups) to get exposure and brush up on your knowledge Betty’s tips for getting involved in these women-oriented coding groups: Put yourself out there Encourage your friends and bring them along Don’t worry — other women will be there and they’re not a judgmental group   Mentioned in this Episode: Betty Pierce’s LinkedIn and Twitter Women Who Code Women Who Code Tampa Girl Develop It Girl Develop It Tampa Bay Girls Who Code Women Who Code Hackathon Meetup Suncoast Developers Guild Suncoast Developers Guild Jr.   Want to Learn More or Get in Touch? Visit the website and catch up with all the episodes on AgileThought.com! Email your thoughts or suggestions to Podcast@AgileThought.com or Tweet @AgileThought using #AgileThoughtPodcast!

Today on the Agile Coaches’ Corner, your host, Dan Neumann invites on Sean Davis to explore the DevOps movement. Sean is one of Dan’s colleagues at AgileThought and is a DevOps expert and frequent conference speaker. He has been a Business Transformation Consultant at AgileThought for nearly two years now and previously was a Technical Advisor at InterContinental Hotel Groups.   In this episode, Dan and Sean explore the background and history behind DevOps, where they believe it is headed in the future, the enablers that help teams be most effective with DevOps, important mindsets to bring to DevOps, as well as both the challenges and benefits of DevOps not having a defined manifesto or framework.   Key Takeaways Challenges Sean sees the most without a manifesto in terms of defining good DevOps: It is harder to get education around it Lack of standardization Lots of interpretations of what DevOps is The benefits of DevOps not having a defined manifesto or framework: Freedom to create different frameworks around what works best for a customer or organization so it’s much more adaptive A supported culture of collaboration Able to adapt and grow more easily over the years Continuous learning Important mindsets to bring into DevOps: Focus on connecting the dots of Dev and Ops Work together as a team and articulate that to the business Get every stakeholder of the business involved Don’t do things in a vacuum Learn from every experience, good or bad Effectively debrief so you’re continuously improving and learning A strong culture with expectations Where Sean sees DevOps headed and where he thinks it should head: A possible name change as the name itself is limiting Not to think of DevOps in such a narrow way and instead, think of how to radiate it throughout the entire organization Be more careful about building silos in communities Move towards a model similar to ADAPT (which ties together Transformation, Agile, DevOps, and Product all into one executable transformation) DevSecOps and a greater culture of collaboration   Mentioned in this Episode: Sean Davis (LinkedIn) Agile Manifesto Patrick Debois (AKA the Godfather of DevOps) John Willis’ framework, CAMS DevOps Institute ITSM Academy Gene Kim’s ‘Three Ways’ Scrum DevSecOps Azure Terraform Xebialabs VSTS (Azure DevOps) Derek Wade Tom Gilmore, creator of ADAPT   Sean Davis’ Book Picks The Phoenix Project: A Novel about IT, DevOps, and Helping Your Business Win, by Gene Kim, Kevin Behr, and George Spafford Reinventing Organizations, by Frederic Laloux   Want to Learn More or Get in Touch? Visit the website and catch up with all the episodes on AgileThought.com! Email your thoughts or suggestions to Podcast@AgileThought.com or Tweet @AgileThought using #AgileThoughtPodcast!

Joining Dan Neumann today is returning guest, Adam Ulery, a colleague of his at AgileThought.   Adam is a perpetually curious, continuous learner who is always willing to encourage others to try new things (as he very often does himself). As a Sr. Agile Coach and multifamily investor, he’s very focused on helping organizations clarify and meet their business outcomes and loves to help companies become resilient and rediscover their curiosity.   This week, Dan and Adam explore some facilitation tips. Facilitation is an incredibly important skill for many different roles, so in this episode, Dan and Adam explore both basic tips as well as some pro tips. There are many great, key takeaways on how you, as a facilitator, should handle the group, prepare accordingly, use effective tools to gain consensus during meetings, and allow your group to make the most of the meet-up and get where they need to go.   Key Takeaways Types of roles that need solid facilitation skills: Scrum master Any type of coach (Agile or otherwise) Anyone who’s going to be leading meetings, workshops, or training What types of events facilitation skills are used for? Sprint planning, daily Scrums, sprint reviews, and retrospectives Workshops where you’re trying to teach a concept to a group of people Release planning or quarterly planning events The basics of good facilitation: As a facilitator, you should be preparing in advance, getting info radiators up, and understand the goal of the session Information radiators should be concise, clear, valuable, seen by everyone, and include the agenda, parking lot, and working agreement A good room setup (including big flip charts or large amounts of whiteboards) Clarify the roles in the meeting Really utilize the parking lot tool to table items without the risk of losing sight of them and be able to continue to discuss the important topics at hand Useful facilitator tools/deciding tactics for gaining consensus or attention: Roman voting Fist of five Show of hands for a simple yes or no decision Raise your hand, quietly Dot voting (to narrow down topics) Adam’s Pro facilitation tips: Let the group make the decision; the facilitator should remain neutral and not drive the group to make a particular decision If you must wear two hats, make it clear when you’re switching from facilitator to group member Control your own reactions to not influence your audience Actively listen and clarify (even if it seems obvious) Work hard to stay out of their way, be self-aware, and allow them to get where they’re going Encourage workflow and be the guardrails Allow people to be heard but don’t let them take over the conversation   Mentioned in this Episode: Roman voting Fist of five Dot voting Eric Landes (LinkedIn) Agile Coaches’ Corner episode with Eric Landes   Adam Ulery’s Book Picks Ben Franklin: America’s Original Entrepreneur, by Blaine McCormick and Benjamin Franklin Thinking, Fast and Slow, by Daniel Kahneman Rich Dad’s CASHFLOW Quadrant: Rich Dad’s Guide to Financial Freedom, by Robert Kiyosaki   Want to Learn More or Get in Touch? Visit the website and catch up with all the episodes on AgileThought.com! Email your thoughts or suggestions to Podcast@AgileThought.com or Tweet @AgileThought using #AgileThoughtPodcast!

Agile Coach Sam Falco and host Dan Neumann discuss effective retrospectives, covering phases like 'setting the stage' and generating insights, stressing accountability and actionable steps, and exploring Liberating Structures and Kaizen. They also touch on distributed retrospective tools and sports referee bias.

Today on the Agile Coaches’ Corner, Dan Neumann is joined by Ryan Dorrell, the Chief Solutions Officer, and one of the co-founders of AgileThought. He leads the strategic design of their portfolio of offerings and services across their practice areas, focusing on understanding what the future looks like for their clients and how they can best serve them.   In this episode, Dan and Ryan explore the topic of product management. Ryan explains what it is, the ideal skill set and thinking that goes into it, the benefits, and his own tips and techniques around it. He also goes in-depth about the differences between projects vs. products — and why you really should be joining the #noprojects movement!   Key Takeaways What is (software) product management? And what goes into it? A lot of creativity, diverse skill set, and a different mindset around solving problems Continuously delivering value and aligning with products and services that provide to customers Solves a problem in a unique way Engaging with customers for feedback loops Customer journey maps, user story mapping, design thinking, and workshops The benefits of product management: Builds empathy with customers and focuses on understanding their needs Addresses the user experience Helps to make systems more delightful and engaging to use Ryan’s tips and techniques around product management: Go start learning and understanding the aspect of taking products to market Be prepared to learn a lot of new skills and techniques ● Projects vs. Products: A project is a temporary endeavor (to create a product or service) with a deadline A product satisfies a need, a want, or solves a problem and continuously evolves with customers/users feedback With product management, there is less focus on timesheets and more focus on the product itself Projects stop and start, while products respond to change Mentioned in this Episode: Chris Spagnuolo Twitter (products vs. projects): #NoProjects Ryan Dorrell’s Book Picks User Story Mapping: Discover the Whole Story, Build the Right Product, by Jeff Patton Project to Product: How to Survive and Thrive in the Age of Digital Disruption with the Flow Framework, by Mik Kersten #noprojects: A Culture of Continuous Value, by Evan Leybourn and Shane Hastie INSPIRED: How to Create Tech Products Customers Love, by Marty Cagan Mapping Experiences: A Complete Guide to Creating Value through Journeys, Blueprints, and Diagrams, by James Kalbach Want to Learn More or Get in Touch? Visit the website and catch up with all the episodes on AgileThought.com! Email your thoughts or suggestions to Podcast@AgileThought.com or Tweet @AgileThought using #AgileThoughtPodcast!

Return guest, Quincy Jordan, is joining Dan Neumann once again! Quincy is a Principal Transformation Consultant and has been with AgileThought for about one year now. Previous to that, he has served as a Principal Consultant and Agile Coach at SCRUMstudy.com for over six years. Quincy’s mission is to help companies and people who are ineffective in their own mission by assisting them in transforming from what they are to what they desire to be. This week they’re getting their hands dirty and talking about living off the Agile landscape. Quincy explains the differences between Agile “Gardening” vs. Agile “Farming,” where the Agile farming metaphor came from, and key “farming” practices.   Key Takeaways The background behind the Agile landscape “farming” metaphor: In farming and gardens, there is great attention to detail and a lot of care put into it, similar to the nurturing needed with Agile Agile Gardening vs. Agile Farming: What you need depends on the business outcomes you’re trying to achieve Agile farming requires thinking outside of your immediate environment and scaling beyond your environment Inward benefits from agile gardening vs. outward benefits from agile farming One isn’t better than the other but it is important to choose the right tool When scaling: Programmers should pull back their vantage point to get a more aerial view, focusing on overall outcomes and things going on in the environment Teams need a vantage point that is an up-close picture to really see all the detail Key Farming Practices: Farmers need to actively protect the environment Just like farmers use crop rotation for soil depletion, it is important to rotate teams to avoid transformation (or Agile) fatigue Rotation needs to take place, whether you rotate teams across different functions or rotate within the team Keep the team together regardless of how you’re rotating it When an environment is new, similar to a farm, they have to ready the soil of the environment Preparation is key If you want teams to collaborate well, an accommodating, structured environment needs to be prepared for the team Farmers must be concerned with “where” before “what,” and “timing” before “time”   Mentioned in this Episode: Tampa Bay Agile Meetup SAFe Model Agile Coaches’ Corner episode: “Communities of Practice with Quincy Jordan”   Quincy Jordan’s Book Pick The Age of Agile: How Smart Companies Are Transforming the Way Work Gets Done, by Stephen Denning   Want to Learn More or Get in Touch? Visit the website and catch up with all the episodes on AgileThought.com! Email your thoughts or suggestions to Podcast@AgileThought.com or Tweet @AgileThought using #AgileThoughtPodcast!

In today’s episode of the Agile Coaches’ Corner, your host, Dan Neumann, and his guest, Adam Ulery, will be exploring an experimental mindset. Adam is one of Dan’s colleagues at AgileThought. Adam is a perpetually curious, continuous learner who is always willing to encourage others to try new things (as he very often does himself). He’s a Sr. Agile Coach and multifamily investor. He’s focused on helping organizations clarify and meet their business outcomes and loves to help companies become resilient, rediscover curiosity, and change their traditional approach to business. Dan and Adam explore both the ‘experimental’ and the ‘mindset’ side of an experimental mindset, fully explaining what it is, how it’s used, the importance of it, and the benefits. They also highlight how to successfully set out to experiment and some of the key learning that can come from implementing it.   Key Takeaways What is an ‘experimental mindset?’ Trying something new or different to see if it will work with an intention Intentional about what you’re setting out to learn (through a hypothesis) and then measuring results How to successfully set out to experiment: Begin with an end in mind (i.e. know what you’re setting out to achieve) Be curious and start asking questions Have a general awareness as a team and notice patterns to identify areas that may need experimenting (i.e. “what would happen if…?”) Begin collecting data to help identify patterns The importance of ‘mindset’ in an experimental mindset: Being open and willing to try new things Approaching it with a genuine curiosity The benefits of an experimental mindset: The results will always be valuable regardless of the outcome They are small, safe experiments (vs. big, risky bets) Provides valuable learning outcomes that mitigate risk Key Learnings: Experimental mindset is being intentional about what you’re setting out to learn It’s important to have an open mind and approach things with a genuine curiosity Identify patterns through collecting data to pinpoint areas that may need experimenting Mentioned in this Episode: Adam Ulery (LinkedIn) Adam Ulery’s Book Picks Dare to Lead: Brave Work. Tough Conversations. Whole Hearts., by Brené Brown Principles: Life and Work, by Ray Dalio The Age of Agile: How Smart Companies Are Transforming the Way Work Gets Done, by Stephen Denning Crushing It in Apartments and Commercial Real Estate: How a Small Investor Can Make It Big, by Brian H. Murray Want to Learn More or Get in Touch? Visit the website and catch up with all the episodes on AgileThought.com! Email your thoughts or suggestions to Podcast@AgileThought.com or Tweet @AgileThought using #AgileThoughtPodcast!

In this episode, Christy Erbeck, Principal Transformation Consultant, and Dan Neumann discuss the importance of working agreements. They talk about establishing core working hours, creating a safe working environment, and setting a clear path for the team's future. They also provide tips on how to create a working agreement with a new team and the significance of incorporating fun and humor. Additionally, they discuss their experiences with 'The Age of Agile' and 'Dare to Lead' books.

Joining Dan Neumann today is one of his AgileThought colleagues, Quincy Jordan.   Quincy is a Principal Transformation Consultant and has been with AgileThought for about one year now. Previous to that, he has served as a Principal Consultant and Agile Coach at SCRUMstudy.com for over six years. Quincy’s mission is to help companies and people who are ineffective in their own mission by assisting them in transforming from what they are to what they desire to be.   In today’s episode, Quincy explains what exactly a community or practice is, what it can be used for, and why it can be so beneficial to an organization. He also gives his tips on how to effectively use a community of practice as well as how to get it started and incentivize others to show up.   Key Takeaways What is a community of practice? A group or body of individuals that have a common interest or practice As a group, they come together to finetune their craft Can be formal or informal It is not mandatory and is open to anyone (you only need an interest to show up) What can communities of practice be used for? A mechanism for transformation within a company or organization Knowledge transfer across teams Improve and transform the culture Bring teams together and improve communication throughout an organization Quincy’s tips on how to effectively use a community of practice: Invite in guest speakers from another community of practice It will only be as effective as it is supported (a sponsor or team is key) How to get a community started and incentivize others to show up: Food — seriously! Led by a team (also known as “champions”); not an individual As a “champion,” you gain high visibility within the organization Be conscious of timing — make it convenient for people to show up Get a sponsor on board to help with some of the organizational hurdles Find a suitable location Establish a clear purpose (every time the community meets) Key Learnings: Lead your community of practice as a team; not an individual Use your community or practice as a mechanism for transformation Remember that it can only be as effective as it is supported, so be sure to find a sponsor and establish a core team of support Establish a clear purpose at the beginning of every “meeting” to keep the goal in mind   Mentioned in this Episode: Quincy Jordan A Guide to the Scrum Body of Knowledge, by SCRUMstudy SCRUMstudy.com Quincy’s Recent LinkedIn Post Humble Inquiry: The Gentle Art of Asking Instead of Telling, by Edgar H. Schein   Quincy Jordan’s Book Pick What Every Body Is Saying: An Ex-FBI Agent's Guide to Speed-Reading People, by Joe Navarro with Marvin Karlins   Want to Learn More or Get in Touch? Visit the website and catch up with all the episodes on AgileThought.com! Email your thoughts or suggestions to Podcast@AgileThought.com or Tweet @AgileThought using #AgileThoughtPodcast!

Today’s episode of Agile Coaches’ Corner is all about full cycle development. Joining your host is Eric Landes — a colleague of Dan’s and a Scrum.org certified professional Scrum trainer.   Eric comes from a DevOps background, originally starting out as a developer. Currently, he serves as a Senior DevOps Consultant, ALM Director, and Solutions Architect. In his roles, he helps clients deliver value to customers in their software delivery pipeline, and has tons of experience leading organizations in adopting Agile and Lean frameworks, like Scrum and Kanban. His specialties are in Agile Project Management, Lean Software Development, Enterprise Project Management Implementation, and many more.   In this episode, Eric explains what a full cycle developer is, what a full cycle development team looks like, who he sees this model working for, how to take steps towards this model and improving your team, and where to get started. He also gives a ton of recommendations, valuable resources, and actionable tips and tricks you can begin using today.   Key Takeaways What is a full cycle developer? Your development team has all the skills needed to build, deploy, etc. Responsible for the full software lifecycle Your team owns it from beginning to end What to keep in mind when transitioning to Agile or full cycle development: The journey takes a long time and the company needs to support the workers through structure and community A good leader is crucial Who does full cycle development work for? It depends on the context — experiment to find out what works for your team Not everybody; different models for different organizations Identifying the problem you’re trying to solve can indicate which model you should use Steps to take towards improving your DevOps team: Measure to help drive improvement Monitor things in production so you can give feedback to the team on what’s working and what’s not Implement hypothesis-driven development Where to get started on your full cycle development journey: Start with Agile and XP principles if you haven’t already Check out the Netflix Tech Blog Understand the principles and practices of DevOps Be sure to experiment, experiment, experiment Key Learnings: A full cycle developer has a general skill set and is responsible for the whole software lifecycle The transition to Agile or full cycle development takes a long time — the company needs to support their workers in this transition through structure and community The full cycle developer model doesn’t work for all companies; you should experiment to see what works best for your team Drive improvement by measuring data and providing feedback   Mentioned in this Episode: DevOps Enterprise Summit Eric Landes’ LinkedIn Full Cycle Developers (Netflix Model) Woody Zuill’s LinkedIn “7 Habits of Successful DevOps” (with Sam Guckenheimer) Implementing Hypothesis-Driven Development XP Principles Netflix Tech Blog edX   Eric Landes’ Book Picks Turn the Ship Around!: A True Story of Turning Followers into Leaders, by L. David Marquet Training from the Back of the Room!, by Sharon L. Bowman   Want to Learn More or Get in Touch? Visit the website and catch up with all the episodes on AgileThought.com! Email your thoughts or suggestions to Podcast@AgileThought.com or Tweet @AgileThought using #AgileThoughtPodcast!