Leadership alignment itself is a journey
We're motivated, and we know where we want to go... wait, hold on, not everyone is on the bus yet!
After working primarily with the creative director and the rest of the production team, it was time to engage with the whole leadership team, which included about eight more people.
We also started getting calls and emails from leaders above the creative department asking what exactly we were doing. They became aware because of my research interviews and were curious about what we were up to.
If you're going to run Creative Scrum in your organization, you're going to need alignment from a wide variety of people. Two key steps in this part of the journey are:
This post if part of a Creative Scrum series where we explore the how to apply agile for creative teams.
On one call, our production team quickly cranked out a list of benefits. It looked like this:
It wasn't organized or crisply messaged, but we had a list, and that's a good place to start. This list was our success bucket for creative scrum, containing all the aspects of how it would make things better.
If you haven't already, take a few minutes and write out your list of benefits that you believe will result from implementing creative scrum.
How we communicated the benefits changed based on who we we're talking to. The content didn't change, but how it was packaged did. Two key factors guided how we communicated the benefits.
It's so natural to explain things from our own perspective and share the details we see as important. Your communication will be much more effective when you approach it from your audience's perspective.
The goal of these before and after meetings is a combination of understanding, empathy and alignment.
I had a main slide deck including most of the critical information, like benefits, overarching concepts and details. I never shared that deck. I made various versions of it depending on who I was communicating with.
For each, I would consider, "What are the questions they want answered? What is most important to them?"
This discipline of contextualization not only improved my communication but also improved my design. As I would look from another perspective, I would see a potential opportunity or pain point that had been hiding in the background from my previous vantage point.
Here are some steps to get you started:
We had lots of meetings. More about that in the next post too. Many of the meetings had a large number of people, and often I wasn't in charge of the agenda. Most of them were an extension of a previous meeting that didn't resolve or an extension of an extension of an extension.
This isn't how I would recommend conducting meetings. I'm an advocate for meetings with clear outcomes, scope, and resolution. But sometimes, we aren't running the meetings, and we need to adapt.
Going into a meeting, you should know one of the key outcomes or at least the topic or problem being addressed.
Depending on the topic, I would connect with key people to see what they were thinking. If there were major concerns or questions. Since I was the subject matter expert of Scrum, there were often many questions of "how?" and "why?"
Getting on smaller calls allowed others to ask these questions and work through the framework at their own pace.
This usually helped create a common understanding as a foundation for the discussion and decisions during the meeting. When we didn't have that common foundation, it was really evident and not fun.
Scrum has a lot of meetings and it can be hard to keep them straight, especially when you're getting started.
The Scrum meeting checklist has all the details you need to run effective Scrum meetings.
During a meeting, does somebody seems angry, confused or really quiet? These are all good reasons to reach out and connect afterward.
Was there a misunderstanding? Did they not agree with the decision?
Often this might start as a Slack message link, "what did you think of the meeting?" Sometimes the conversation stayed in Slack. Other times it became a phone or zoom call.
The goal of these before and after meetings is a combination of understanding, empathy and alignment. They can feel like they take a lot of time, but they actually save time in the long run.
As I would look from another perspective, I would see a potential opportunity or pain point that had been hiding in the background from my previous vantage point.
This is especially true when you consider the shared hours used when ten people spend two hours on an unproductive call. That's half a workweek!
So take the time and put in the work to communicate and connect with others as you begin to sell your ideas more broadly.
If you're going to run Creative Scrum in your organization, you're going to need alignment from a wide variety of people. Two key steps in this part of the journey are:
Important factors include your team size and the type of work you do. Kanban is very process-oriented, so you should consider how defined, static, or long your process is?
You can explore Scrum and other agile approaches. Then browse the most common terms in a Scrum glossary and learn what is Scrum.
Scrum forces clarity and prioritization, which are critical to organizational effectiveness. It provides a competitive edge by allowing teams to adapt as the market or priorities change. Teams operate more effectively because Scrum combines empowerment of the team members with alignment to top priorities.
Learn more about scrum’s impact on organizational culture. Then browse the most common terms in a Scrum glossary and learn what is Scrum.
Scrum is more of a framework than a methodology, and it helps teams adhere to Agile principles and get stuff done. Scrum provides basic rules but doesn’t prescribe how to do the work. It provides principles, values, rules, and some core structure but still leaves a lot undefined.
Learn more about scrum as a framework. Then browse the most common terms in a Scrum glossary and learn what is Scrum.
When people say “agile,” they usually refer to it as a mindset. Scrum is a framework for how to organize people and work in an agile way. If you’re practicing Scrum, you’re working in an Agile way.
Learn more about the relationship between scrum and agile. Then browse the most common terms in a Scrum glossary and learn what is Scrum.
Scrum is founded on three essential pillars leading teams to ask the following questions:
Further explore the definition of scrum. Then browse the most common terms in a Scrum glossary and learn what is Scrum.
This is because Scrum’s simplicity makes learning easy, but Scrum truly changes how you work, and that adjustment can be difficult. It changes power dynamics and expectations within the team and between the team and the rest of the organization.
You can explore further is Scrum hard to learn, along with the pros and cons of Scrum. Then browse the most common terms in a Scrum glossary and learn what is Scrum.
Scrum was initially used as a term related to project management in 1986 by Hirotaka Takeuchi and Ikujiro Nonaka in their paper “New New Product Development Game” In the Harvard Business Review. The first recorded Scrum project came a little later in 1993 from Jeff Sutherland.
You can learn more about Scrum’s backstory. Then browse the most common terms in a Scrum glossary and learn what is Scrum.
Learning Scrum for the first time can be overwhelming. There are a lot of new terms and concepts in Scrum. I’ve listed the most common terms in a Scrum glossary.
It forces clarity and prioritization, which provides the focus necessary for teams to be effective. Scrum embraces complexity and change by keeping many things simple and iteratively evaluating and adapting.
You can learn more about why to use Scrum and three challenges Scrum solves. Then browse the most common terms in a Scrum glossary and learn what is Scrum.
Scrum isn’t always the best option for teams. Scrum can fail when there is a substantial mismatch between organizational culture and the Scrum values. It also depends on the nature of the work you do. If you work if very linear, predictable and tightly defined, you may not experience many benefits Scrum provides.
Find out more about aligning your organizational values with Scrum or how Scrum might fit in your context. Then browse the most common terms in a Scrum glossary and learn what is Scrum.
Scrum functions at its best when you have a dedicated team focused on developing a singular product. Its agility shines when there are time constraints combined with uncertainty.
Explore the pros and cons of Scrum along with expectations vs. realities with Scrum. Then browse the most common terms in a Scrum glossary and learn what is Scrum.
Scrum is founded on three essential pillars, and each leads the team to ask a critical question.
Learn how to apply the three pillars of Scrum and then explore the most common terms in a Scrum glossary.
There are five values critical to the practice of Scrum: commitment, courage, focus, openness, and respect.
Learn how to align Scrum values with your organization and then explore the most common terms in a Scrum glossary.
The sprint goal encapsulates the product owner’s vision into a concrete statement for the development team to measure the sprint against. The sprint goal provides a theme for the sprint’s work helping the team see how all the parts come together.
Learn more about the role of the sprint goal in scrum and explore the essential Scrum glossary.
Are you striving to align your goals with your values and passions?
Wondering how to measure progress or break down large goals into manageable steps?
Are you ready to transform your dreams into reality?
Our Goal Focus Guide + Worksheet is designed for you to discover how effective goal setting can transform your personal and professional life.
Download the Goal Focus Worksheet