Hello, I’m Martin Hinshelwood, the owner of Naked Agility based in Glasgow, Scotland. Today, I want to share some insights and experiences that have come up in recent discussions, particularly around remote working, the integration of UX in Agile practices, and the importance of team dynamics.
Embracing Remote Work
As many of us find ourselves navigating the complexities of remote work, it’s crucial to remember that while Scrum promotes co-located teams, the reality is often different. Here are some key points to consider:
-
Communication is Key: Are you regularly checking in with your teammates? It’s vital to maintain open lines of communication, even if it’s through video conferencing. Make sure everyone knows what others are working on to foster a sense of collaboration.
-
Adapt Your Tools: Don’t get stuck using tools that aren’t serving your needs. I recently tried using Microsoft Teams for a web conference and found it lacking for my specific setup. Be willing to experiment with different technologies to find what works best for your team.
-
Focus on Value Delivery: While remote work can sometimes lead to a lack of focus, it’s essential to keep delivering value. Remember, the work we do in Scrum is complex and requires a thoughtful approach to problem-solving.
The Production Line Analogy
In the realm of software development, I often refer to the concept of a “production line.” This analogy helps us understand the flow from idea to working software. Here’s how to think about it:
-
Zero Build Time: Inspired by Brian Harry’s concept of zero build, consider how long it takes to get a version of your product into production without any changes. This metric can help you identify bottlenecks in your process.
-
Feedback Loops: To improve your production line, gather feedback at every stage. This will help you refine your processes and ensure that you’re building the right thing.
Team Dynamics and Gamification
One of the most rewarding aspects of Agile is the emphasis on teamwork. Recently, I’ve been exploring how gamification can enhance team collaboration. For instance, playing cooperative games like Pandemic can reveal dynamics within your team. Here’s what I’ve learned:
-
Observation is Crucial: During gameplay, observe how team members interact. Are there dominant voices? How can you ensure everyone’s opinion is heard? This reflection can lead to valuable discussions about team dynamics.
-
Create a Safe Environment: Games provide a fun, low-stakes way to experiment with team interactions. Use these opportunities to foster open dialogue about collaboration and communication.
Integrating UX into Agile Practices
A question I often receive is how to ensure that UX isn’t an afterthought in larger organisations. Here’s my take:
-
Involve UX Early: It’s essential to integrate UX skills within your Scrum teams. The UX community plays a critical role in understanding user needs and behaviours, which should be a priority from the outset.
-
Dual Track Approach: The concept of dual track Agile allows teams to move between discovery and delivery modes. This means that while some team members are focused on building, others can explore user feedback and insights.
-
Team Accountability: Everyone on the team should share responsibility for delivering a great user experience. This collective accountability ensures that UX considerations are woven into every aspect of product development.
Conclusion
In summary, whether you’re navigating the challenges of remote work, striving for engineering excellence, or integrating UX into your Agile practices, the core values of Scrum, transparency, trust, and collaboration, should guide your efforts.
As we continue to adapt to these changing circumstances, let’s remember to focus on our people and the value we deliver. If you have any questions or would like to discuss these topics further, please don’t hesitate to reach out.
Thank you for taking the time to read this, and I hope you found these insights helpful. Let’s keep the conversation going!
Smart Classifications
Each classification [Concepts, Categories, & Tags] was assigned using AI-powered semantic analysis and scored across relevance, depth, and alignment. Final decisions? Still human. Always traceable. Hover to see how it applies.
What to read next
Mastering Agile in a Distributed World: Tools and Strategies for Effective Team Management
Explore practical tools and strategies for managing Agile teams in distributed environments, including communication tips, tool comparisons, …
Navigating Agile Transformation: Empowering Teams for Success in a Rapidly Changing Landscape
Explores effective Agile transformation by empowering teams, improving collaboration, focusing on value delivery, and fostering continuous …
Unlocking the True Power of Agile: Embracing Change and Collaboration for Team Success
Explores how Agile success relies on team collaboration, embracing change, continuous improvement, and focusing on delivering real value to …
Maximise Your Scrum Process: Leveraging Azure DevOps for Agile Success
Learn how to customise Azure DevOps to support Scrum teams, manage backlogs, plan sprints, and improve agile workflows with practical setup …
Scaling Agility: Navigating the Dragons of Change in the Future of Work
Explores practical strategies for scaling agile practices, key metrics, virtual training adaptations, and global insights to navigate change …
What is your perspective on collocation?
Explores the benefits and challenges of collocation in Scrum teams, comparing face-to-face collaboration with remote work, and offering …
Detecting agile theatre with real delivery signals
Why Most Companies Operating Models Fail in Dynamic Markets
A concise comparison of Predictive and Adaptive Operating Models, explaining why traditional structures fail in dynamic markets and how …
Don’t Manage Dependencies, Remove Them
Explains why dependencies are a sign of poor system design and outlines steps to eliminate them by aligning teams, clarifying ownership, and …
The Estimation Trap: How Tracking Accuracy Undermines Trust, Flow, and Value in Software Delivery
Tracking estimation accuracy in software delivery leads to mistrust, fear, and distorted behaviours. Focus on customer value, flow, and …
Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?
Compares “flow of value” and “flow of work” in Kanban, explaining why only validated outcomes count as value and stressing the need for …
Why Outsourcing DevOps Fails, and How Real Engineering Excellence Starts With Your Team
Avoid DevOps vendor lock-in, discover how true engineering excellence starts with partnership, not outsourcing. Ready to transform your …
Why Most Companies Operating Models Fail in Dynamic Markets
A concise comparison of Predictive and Adaptive Operating Models, explaining why traditional structures fail in dynamic markets and how …
Don’t Manage Dependencies, Remove Them
Explains why dependencies are a sign of poor system design and outlines steps to eliminate them by aligning teams, clarifying ownership, and …
The Estimation Trap: How Tracking Accuracy Undermines Trust, Flow, and Value in Software Delivery
Tracking estimation accuracy in software delivery leads to mistrust, fear, and distorted behaviours. Focus on customer value, flow, and …
Kendall Guide - A System of Work for AI Adoption
Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?
Compares “flow of value” and “flow of work” in Kanban, explaining why only validated outcomes count as value and stressing the need for …
Estimating Better in an Overloaded System Is a Poor Man’s Strategy
High work in progress (WIP) causes delays and unpredictability; improving estimates won’t help. Limiting WIP and focusing on flow is key to …
The Definition of Done is a Commitment to Quality
Defines the Definition of Done in Scrum as a clear, shared standard for quality, ensuring increments are releasable, transparent, and …
Why Your Definition of “Done” Is Holding Back Quality, Agility, and Trust, And How to Raise the Bar
Is your team’s “done” really done? Discover how a clear, objective definition of done boosts quality, agility, and trust in product …
Acceptance Criteria vs Definition of Done: Why Getting This Right Builds Trust and Delivers Quality Faster
Stop confusing acceptance criteria with definition of done, learn the crucial difference to boost quality, speed, and trust in your agile …
How to Evolve Your Definition of Done: Start Small, Grow Smarter, and Build Lasting Momentum
Unlock a smarter Definition of Done, start small, evolve standards, and build team momentum without overwhelm. Discover how progress drives …
Why Most Transformations Fail Without Honest Conversations
Most transformations fail without open, honest conversations that address real issues, making transparency and tough dialogue essential for …
Why Your Definition of Done Is the Secret Weapon for Real Business Impact and Agile Growth
Transform your definition of done into a strategic advantage, deliver real value, reduce risk, and drive business impact with every sprint.