Ralph Maria Jocham's Blog, page 21

What Should a Product Owner Achieve in the First 90 days?

In any Scrum Team, the Product Owner plays a  maintenance pivotal role in ensuring successful product delivery to customers through supporting, monitoring and steering their team in the direction they need to go. Without a Product Owner, teams risk losing sight of their end goal, have communication and expectation issues with Stakeholders and customers, as well as damage to productivity and overall performance. At the end of the day, Product Owners must ensure and achieve maximum value for the organisation by collaborating closely with the Development Team and ensuring all product requirements are defined and executed on time. Doing due diligence to achieve this as a Product Owner therefore involves taking accountability for your actions and your responsibilities, as well as taking an active role in furthering your understanding and knowledge of Scrum and Product Ownership so that you can better serve your team, the organisation and the customers.  

But if you are familiar with the world of Product Ownership and not exactly sure where to start or what to do, do not sweat! Your first day as a Product Owner will naturally feel intimidating as you step into a role where all eyes are on you and people are depending on you. However with some basic checkpoints and steps, you can work with confidence knowing that you are staying on the right track. And a really great way to remain accountable and proactive in this role is to follow a guideline on what you should achieve as a Product Owner within your first thirty days.  

The 90-Day Rule  

If you have worked with people before, I am sure you have heard them say many times that they actually do not know what they are doing and are just learning along the way. I have met many people like this during my career and personally I feel that this is wrong. I think this is the wrong attitude to have because it is always important to have a clear point of where you want to go and be working towards a particular vision. So with that being said, here are some of the things I think all Product Owners should be able to achieve within their first 90 days on the job.  

Number One: Have a Good Product Vision.  

As stated above it is always always good to have a vision on where you want to go.  Having a good Product Vision and then being able to communicate that effectively to the rest of your team as well as the Stakeholders will help your team align and work together towards the same goal. In Scrum, the Product Vision refers to the future state of a product that you and your team wish to arrive at and ideally serves as a point of reference for your product and the common objectives within the team. Having a clearly defined Product Vision will not only help you make sense of what it is you are actually doing but as you move along, you will be able to break it up into smaller parts, leading to a more developed plan that can be used in later projects.  

 So with that being said, a Product Vision answers:  

 A definition of done. 

How the final product should function.  

Who it is being built for and how it addresses their needs.  

Once you have that, the next thing you need to look at is what the ‘Definition of Done’ looks like.  

Number Two: Definition of Done 

A Definition of Done is an agreed-upon set of items that must be completed before a project or user story can be considered complete. This is applied consistently and serves as a guideline for the difference between ‘in-progress’ and ‘done.’ The benefits of having a clear definition of done is that it can help ensure that teams are aligned across stages of the production process and that they can continue working towards these objectives even without the presence of the Product Owner. Determining whether a team is meeting the definition of done is typically looked at in the Sprint Review, and is opportunity for teams and the Product Owner to review their work processes and whether they are on the right track.  

Number Three: Sprint Review  

Last but not least if you want to ensure your team is continually meeting their targets and remaining motivated, it is important to conduct meaningful Sprint Reviews. This is because if your Sprint Review is boring, lacks purpose or direction, nobody will want to come and the result of that will be a demotivated team. So ditch the simple powerpoint slides and use the opportunity to collaborate transparency with your team, analyse your definition of done and collectively identify any barriers against achieving your goals.  

Value is Our Target 

In the end our focus is on our customers and delivering high-product quality to them continually. But without a strong healthy foundation which is the team or the organisation, this cannot be achieved.  

 

If you are interested in learning more about how to be an impactful Product Owner, get in touch with Ralph today! 

Ralph Jocham is a Change Agent in Scrum // Agile // Coaching // Evidence Based Management and also a Professional Scrum Trainer based in Europe. 

As one of the first Professional Scrum Trainers in the world, Ralph has worked directly with cocreator of #scrum, Ken Schwaber, and has played an integral part in the course development of the #PSPO (Professional Scrum Product Owner) as well as the delivery of all #scrum.org certified courses. 

If you’re looking to invest in training that transforms and empowers teams to successfully adopt #scrum or #agile, and create high-performance #productdevelopment environments leveraging the agile values and principles, visit https://effectiveagile.com/agile-scru... 

If you would like to work with Ralph and company as an #agilecoach, #agileconsultant, or powerful change agent to get your team back on track and on the road to high-performance #agile #productdevelopment, visit https://effectiveagile.com/agile-tran... 

For more great ‘how-to’ videos, blogs, and insights, subscribe to this channel and visit https://effectiveagile.com/blog/ for more valuable content. 

#scrum #agile #scrumorg #scrumcertification #scrumcourses #scrumtraining #agilescrumtraining #agilekata #agility #businessagility #agileprojectmanagement #projectmanagement #productdevelopment #agileproductdevelopment #switzerland #germany #europe #scrumteam #scrumframework #professionalscrumtrainer #PST #certifiedscrumtrainer #certifiedscrumtraining 

 

Things nobody tells you about product ownership. Part 1

There is no room for excuses because you have the power to make all the necessary decisions. This can be a challenging aspect of the role, as some people handle it well while others struggle.

Things nobody tells you about product ownership – Part 1

Product ownership is a role that requires certain qualities and responsibilities in order to succeed. There are a number critical aspects that are not typically taught when stepping into this role, but they’re absolutely essential to becoming a successful product owner. Let’s unpack the first, and perhaps, most important of these: authority and accountability.

The role of authority and power in Product Ownership

The entire organisation must respect the authority and power that comes with being a product owner. As the product owner, you have the ability to make all decisions regarding the product. This freedom to shape and steer the product’s direction is a profound responsibility and a testament to the trust your organisation places in you.

The authority that comes with product ownership isn’t simply handed over; it is earned through demonstrating sound judgement, making informed decisions, and delivering value.

Balancing power with accountability

However, it is important to remember that with authority also comes accountability. This connection is a fundamental aspect of product ownership and one that cannot be overlooked. As the product owner, if something goes wrong with the product, you are the one who is ultimately responsible.

Here’s the catch: along with the power to make all necessary decisions, there is no room for excuses. You are expected to own up to any mishaps, errors or failures. Being in a position of such authority, you are the go-to person for answers and solutions when things don’t go as planned. This aspect of the role can indeed be challenging. It’s a facet of product ownership that some handle well, while others struggle.

Stay tuned as we dive deeper into the other unspoken aspects of product ownership in upcoming posts. It’s a journey, and I’m here to guide you through every step of the way.

About Effective Agile

Ralph Jocham is a Change Agent in Scrum // Agile // Coaching // Evidence Based Management and also a Professional Scrum Trainer based in Europe.

As one of the first Professional Scrum Trainers in the world, Ralph has worked directly with cocreator of #scrum, Ken Schwaber, and has played an integral part in the course development of the #PSPO (Professional Scrum Product Owner) as well as the delivery of all #scrum.org certified courses.

If you’re looking to invest in training that transforms and empowers teams to successfully adopt #scrum or #agile, and create high-performance #productdevelopment environments leveraging the agile values and principles, visit https://effectiveagile.com/agile-scru...

If you would like to work with Ralph and company as an #agilecoach, #agileconsultant, or powerful change agent to get your team back on track and on the road to high-performance #agile #productdevelopment, visit https://effectiveagile.com/agile-tran...

For more great ‘how-to’ videos, blogs, and insights, subscribe to this channel and visit https://effectiveagile.com/blog/ for more valuable content.

#scrum #agile #scrumorg #scrumcertification #scrumcourses #scrumtraining #agilescrumtraining #agilekata #agility #businessagility #agileprojectmanagement #projectmanagement #productdevelopment #agileproductdevelopment #switzerland #germany #europe #scrumteam #scrumframework #professionalscrumtrainer #PST #certifiedscrumtrainer #certifiedscrumtraining

What don’t new product owners know but really should?

In my training, I often have people who are stepping into the role of Product Owner into the role. Most are keen to get to grips with the tangible tasks, like creating product backlogs or writing user stories. No doubt, these are important elements. But they represent only a small fraction of the role. There’s so much more to the job.

The art of stakeholder management

Perhaps the most vital aspect is stakeholder management. It’s not just about listing out requirements or drafting documents; it’s about communication and understanding.

Engage and connect:

Talk to your users. Understand their needs, their pain points, and their aspirations.

Immerse yourself in their mindset. What challenges them? What delights them?

Bridge the gap with developers:

Communicate what you’ve learned to the developers.

Consider introducing the developers directly to the users. This direct communication can sometimes bridge gaps that no amount of documentation can.

As a product owner, you should ideally be the living representation of everything that’s needed in a value stream. It’s about taking the original idea from its inception and ensuring that the end-user finds a solution to their problem.

Seeing the Bigger Picture

Often, product owners can get caught in the intricacies of day-to-day tasks. It’s easy to lose sight of the big picture.

Strategise and visualise:

Understand the broader implications of the work you’re doing.Grasp the big picture, but be ready to break it down so that developers can act on it.

Validate and review:

Once a task is done, don’t just move on. Bring it back for review.Engage in regular sprint reviews to ensure that the development is aligned with the user’s needs.

New product owners might sometimes feel that their primary role is to sit down and type product backlog items into a tool. However, it’s essential to realise that the job involves so much more.

About Effective Agile

Ralph Jocham is a Change Agent in Scrum // Agile // Coaching // Evidence Based Management and also a Professional Scrum Trainer based in Europe.

As one of the first Professional Scrum Trainers in the world, Ralph has worked directly with cocreator of #scrum, Ken Schwaber, and has played an integral part in the course development of the #PSPO (Professional Scrum Product Owner) as well as the delivery of all #scrum.org certified courses.

If you’re looking to invest in training that transforms and empowers teams to successfully adopt #scrum or #agile, and create high-performance #productdevelopment environments leveraging the agile values and principles, visit https://effectiveagile.com/agile-scru...

If you would like to work with Ralph and company as an #agilecoach, #agileconsultant, or powerful change agent to get your team back on track and on the road to high-performance #agile #productdevelopment, visit https://effectiveagile.com/agile-tran...

For more great ‘how-to’ videos, blogs, and insights, subscribe to this channel and visit https://effectiveagile.com/blog/ for more valuable content.

#scrum #agile #scrumorg #scrumcertification #scrumcourses #scrumtraining #agilescrumtraining #agilekata #agility #businessagility #agileprojectmanagement #projectmanagement #productdevelopment #agileproductdevelopment #switzerland #germany #europe #scrumteam #scrumframework #professionalscrumtrainer #PST #certifiedscrumtrainer #certifiedscrumtraining

What are the three most common mistakes you see in product backlog refinement?

The Scrum Guide states that product backlog refinement is the act of breaking down and further defining product backlog items into smaller and more precise items. This is an ongoing activity. However, this process of refinement is often misunderstood in many aspects.

Mistake 1: Fragmenting functionalities into architectural pieces

One common error that pops up frequently is the breakdown of functionality into architectural components. Let’s say you have a specific functionality, and it’s divided into separate product backlog items, each representing a distinct architectural aspect such as the user interface, business logic, and persistence, among others.

This approach, unfortunately, undermines team collaboration. Everyone starts to work on their respective sections in isolation, which not only hampers the exchange of ideas but also dilutes the overarching goal of the product backlog item.

Mistake 2: Assigning names to specific tasks

Another mistake that I often spot during refinement is the assignment of names to individual tasks. This practice might seem like a good way to maintain order, but it inadvertently stifles team collaboration during the Sprint. Because if everyone has just their one task, then they aren’t truly collaborating. In the daily Scrum, they wouldn’t really talk to each other.

In this setup, team members lose the incentive to cooperate, turning the daily Scrum into a less interactive experience. Instead of nurturing an environment where ideas and responsibilities freely flow, everyone ends up being boxed into their specific tasks.

Mistake 3: Getting too technical

The third mistake is becoming overly technical during product backlog refinement. The purpose of refinement is to clarify the “what” we want to achieve, rather than the “how”.

What do we want? The primary objective is to ascertain the acceptance criteria, identify boundary cases, understand non-functional requirements, and decide what needs to be considered.

Discussing the “how” to some extent is okay, but overall, it’s crucial to keep the product backlog refinement focused on the “what”. In other words, keep the conversation centred around understanding the exact requirements and their context, rather than delving into the specific implementation details.

About Effective Agile

Ralph Jocham is a Change Agent in Scrum // Agile // Coaching // Evidence Based Management and also a Professional Scrum Trainer based in Europe.

As one of the first Professional Scrum Trainers in the world, Ralph has worked directly with cocreator of #scrum, Ken Schwaber, and has played an integral part in the course development of the #PSPO (Professional Scrum Product Owner) as well as the delivery of all #scrum.org certified courses.

If you’re looking to invest in training that transforms and empowers teams to successfully adopt #scrum or #agile, and create high-performance #productdevelopment environments leveraging the agile values and principles, visit https://effectiveagile.com/agile-scru...

If you would like to work with Ralph and company as an #agilecoach, #agileconsultant, or powerful change agent to get your team back on track and on the road to high-performance #agile #productdevelopment, visit https://effectiveagile.com/agile-tran...

For more great ‘how-to’ videos, blogs, and insights, subscribe to this channel and visit https://effectiveagile.com/blog/ for more valuable content.

#scrum #agile #scrumorg #scrumcertification #scrumcourses #scrumtraining #agilescrumtraining #agilekata #agility #businessagility #agileprojectmanagement #projectmanagement #productdevelopment #agileproductdevelopment #switzerland #germany #europe #scrumteam #scrumframework #professionalscrumtrainer #PST #certifiedscrumtrainer #certifiedscrumtraining

How much of a difference can a great Product Owner make to an organisation?

In the realm of product ownership, individuals are typically assigned the title of ‘Product Owner’ and, more often than not, they get landed with a heap of requirements or even a comprehensive specification document. What do they do? They diligently key in all this data into a tool like Jira. We call these Product Owners “scribes”. They are masters at quickly translating requirements into neat digital formats.

Technically speaking, yes, these individuals are Product Owners. But the question that arises is: Are they truly effective in their roles? They function more like clerks, diligently executing their tasks. However, the core idea behind assigning a Product Owner in a Scrum team isn’t about keeping a project on time, on scope, or on budget; it’s fundamentally about the value we aim to deliver.

Domain expertise: A step up

Beyond the “scribe” level, we find Product Owners who are deeply familiar with the domain they work in. For instance, I once worked with a Product Owner at a bank who had more than 20 years of experience in dealing with loans. He knew every detail and could answer any question, advising when to be cautious and when to push the boundaries.

The entrepreneurial mindset

Then there’s another tier that goes beyond even this level of domain expertise, what I like to call the entrepreneurial mindset.

This tier represents those visionaries, people with strong ideas, people who know “this is where we need to go” and who have the drive to really pursue it.

From scribe to visionary

If we were to chart this evolution on an X-axis, it would run from ‘scribe’ to ‘business representative’ to ‘entrepreneur’ to ‘visionary’.

However, it’s also crucial to note that as you move further to the right on this X-axis, from scribe to visionary, you usually also move upwards in the organisation. Your standing improves, your impact grows, and more people listen to you. You gain more freedom to chase the objectives you are passionate about.

About Effective Agile

Ralph Jocham is a Change Agent in Scrum // Agile // Coaching // Evidence Based Management and also a Professional Scrum Trainer based in Europe.

As one of the first Professional Scrum Trainers in the world, Ralph has worked directly with cocreator of #scrum, Ken Schwaber, and has played an integral part in the course development of the #PSPO (Professional Scrum Product Owner) as well as the delivery of all #scrum.org certified courses.

If you’re looking to invest in training that transforms and empowers teams to successfully adopt #scrum or #agile, and create high-performance #productdevelopment environments leveraging the agile values and principles, visit https://effectiveagile.com/agile-scru...

If you would like to work with Ralph and company as an #agilecoach, #agileconsultant, or powerful change agent to get your team back on track and on the road to high-performance #agile #productdevelopment, visit https://effectiveagile.com/agile-tran...

For more great ‘how-to’ videos, blogs, and insights, subscribe to this channel and visit https://effectiveagile.com/blog/ for more valuable content.

#scrum #agile #scrumorg #scrumcertification #scrumcourses #scrumtraining #agilescrumtraining #agilekata #agility #businessagility #agileprojectmanagement #projectmanagement #productdevelopment #agileproductdevelopment #switzerland #germany #europe #scrumteam #scrumframework #professionalscrumtrainer #PST #certifiedscrumtrainer #certifiedscrumtraining

Overview of the US Dept of Defense Agile case study

There’s a paper out there called “Status of the Federal Bureau of Investigation (FBI) Implementation of the Sentinel Project”. The Sentinel project, which was launched after the tragic events of September 11. The FBI realised that they possessed a wealth of information but lacked the ability to connect the dots effectively.

The Agile intervention

With a projected timeline of several years and a budget of $500 million, the project got underway. Many years in, they had already spent $450 million and they couldn’t show anything. Nothing really worked there. They had 500 people working on it essentially wasting taxpayers’ money. So, in the US, you basically have to appear before Congress and answer questions about what’s going on there.

Faced with mounting pressure from taxpayers and government entities, the FBI decided to adopt an Agile approach to salvage the Sentinel project. They reduced their development team from 500 to just 50 individuals.  Another paper, “The interim report on the Federal Bureau of Investigations implementation of the Sentinel project”, documents what happened next. They rented the basement of the Watergate building, put those 50 people in there in a war-room kind of set up. A colocation, which is an overall a good practice. This shift aimed to prioritise collaboration and communication, two fundamental principles of Agile development.

Connecting data points

The first step in the Agile intervention was to consult various agencies involved in the project and identify the most critical data points that needed to be connected. Each agency needed to identify their top priority was and whether it aligned with the overall project objective. The development team basically said: “Okay, let’s ignore everything and let’s just implement that”.

By focusing solely on the essential requirements, the development team was able to rapidly implement a functioning solution within a month or two. It was just a small fraction of the overall objective of the Sentinel project, but it was there and it was working.

Impressive results

What makes this case study truly remarkable is the government’s embrace of Agile principles and methodologies. The publicly available documentation on the Sentinel project demonstrates a deep understanding of the benefits of Agile. I don’t think we associate the government with agility. But when you look at this paper, especially the follow-up one from 2012, they mention ‘Agile’ on 11 pages out of 40, which was surprising.

The government – including the military – recognised they’d been wasting so much money of software projects. And so they changed their software development processes to more Agile methodologies as well.

About Effective Agile

Ralph Jocham is a Change Agent in Scrum // Agile // Coaching // Evidence Based Management and also a Professional Scrum Trainer based in Europe.

As one of the first Professional Scrum Trainers in the world, Ralph has worked directly with cocreator of #scrum, Ken Schwaber, and has played an integral part in the course development of the #PSPO (Professional Scrum Product Owner) as well as the delivery of all #scrum.org certified courses.

If you’re looking to invest in training that transforms and empowers teams to successfully adopt #scrum or #agile, and create high-performance #productdevelopment environments leveraging the agile values and principles, visit https://effectiveagile.com/agile-scru...

If you would like to work with Ralph and company as an #agilecoach, #agileconsultant, or powerful change agent to get your team back on track and on the road to high-performance #agile #productdevelopment, visit https://effectiveagile.com/agile-tran...

For more great ‘how-to’ videos, blogs, and insights, subscribe to this channel and visit https://effectiveagile.com/blog/ for more valuable content.

#scrum #agile #scrumorg #scrumcertification #scrumcourses #scrumtraining #agilescrumtraining #agilekata #agility #businessagility #agileprojectmanagement #projectmanagement #productdevelopment #agileproductdevelopment #switzerland #germany #europe #scrumteam #scrumframework #professionalscrumtrainer #PST #certifiedscrumtrainer #certifiedscrumtraining

What is value?

In understanding project management methodologies, the Scrum Guide plays a pivotal role. It clearly states that the protagonist’s responsibility is to maximise the value from the work of the Scrum team. However, this leads us to an interesting question – what exactly is value?

The relativity of value

To me, the concept of value is very similar to beauty. Like beauty, value is in the eye of the beholder. What I appreciate might not be what you appreciate, and vice versa. This makes it imperative for us to understand our target audience. It’s about figuring out the answer to the questions: “For whom are we doing this?” and “Who are we helping?”

The way I like to think about it is by asking whose life are we aiming to improve with what we do?

Once you adopt this mindset, you can start to look at things from their perspective. What do they appreciate? With this understanding, you can then begin to shape your work in ways that create something of real value to them.

The challenge of identifying value

But why is identifying value so difficult for people? I believe it’s because there are diverse levels of value to consider.

Let’s consider functional value, for example, something as simple as a pencil. It writes. It fulfils a job for me. It solves a problem because I can put my ideas on a piece of paper. But in today’s world, this kind of value is often seen as a commodity – it’s expected, and we’re not willing to pay too much for it.

Beyond functional value

The real value, I argue, is found when we go deeper. We must delve into understanding what goes on in people’s heads. What concerns them? What worries them? How can we help them navigate through life, be it professional or personal?

Organisations that can empathise with their end users have a higher potential. And if they manage to translate that understanding into their products, they truly unlock the secret to maximising value.

About Effective Agile

Ralph Jocham is a Change Agent in Scrum // Agile // Coaching // Evidence Based Management and also a Professional Scrum Trainer based in Europe.

As one of the first Professional Scrum Trainers in the world, Ralph has worked directly with cocreator of #scrum, Ken Schwaber, and has played an integral part in the course development of the #PSPO (Professional Scrum Product Owner) as well as the delivery of all #scrum.org certified courses.

If you’re looking to invest in training that transforms and empowers teams to successfully adopt #scrum or #agile, and create high-performance #productdevelopment environments leveraging the agile values and principles, visit https://effectiveagile.com/agile-scru...

If you would like to work with Ralph and company as an #agilecoach, #agileconsultant, or powerful change agent to get your team back on track and on the road to high-performance #agile #productdevelopment, visit https://effectiveagile.com/agile-tran...

For more great ‘how-to’ videos, blogs, and insights, subscribe to this channel and visit https://effectiveagile.com/blog/ for more valuable content.

#scrum #agile #scrumorg #scrumcertification #scrumcourses #scrumtraining #agilescrumtraining #agilekata #agility #businessagility #agileprojectmanagement #projectmanagement #productdevelopment #agileproductdevelopment #switzerland #germany #europe #scrumteam #scrumframework #professionalscrumtrainer #PST #certifiedscrumtrainer #certifiedscrumtraining

Conway’s Law in 60 seconds

Conway’s Law is a concept I’ve encountered many times throughout my career as a software engineer. It essentially states that a product reflects the internal structure of the organisation that’s building it. This can manifest in various ways, most notably when different departments within a company shape the architectural design of the product.

In practice, if an organisation has a well-organised setup, it often leads to an efficient and well-designed product. Conversely, an ill-structured organisation may result in awkward and ineffective architectures. This aspect can be a significant challenge to overcome.

For this reason, it’s perhaps worth reconsidering how we approach architectural design. We might benefit from treating it much like we do software design – asking questions like where information is stored and what the communication paths are. If we align these aspects effectively, we should be able to provide a strong framework for both the organisation and the product.

About Effective Agile

Ralph Jocham is a Change Agent in Scrum // Agile // Coaching // Evidence Based Management and also a Professional Scrum Trainer based in Europe.

As one of the first Professional Scrum Trainers in the world, Ralph has worked directly with cocreator of #scrum, Ken Schwaber, and has played an integral part in the course development of the #PSPO (Professional Scrum Product Owner) as well as the delivery of all #scrum.org certified courses.

If you’re looking to invest in training that transforms and empowers teams to successfully adopt #scrum or #agile, and create high-performance #productdevelopment environments leveraging the agile values and principles, visit https://effectiveagile.com/agile-scru...

If you would like to work with Ralph and company as an #agilecoach, #agileconsultant, or powerful change agent to get your team back on track and on the road to high-performance #agile #productdevelopment, visit https://effectiveagile.com/agile-tran...

For more great ‘how-to’ videos, blogs, and insights, subscribe to this channel and visit https://effectiveagile.com/blog/ for more valuable content.

#scrum #agile #scrumorg #scrumcertification #scrumcourses #scrumtraining #agilescrumtraining #agilekata #agility #businessagility #agileprojectmanagement #projectmanagement #productdevelopment #agileproductdevelopment #switzerland #germany #europe #scrumteam #scrumframework #professionalscrumtrainer #PST #certifiedscrumtrainer #certifiedscrumtraining

Hardest part of writing The Professional Product Owner book?

Writing a book takes a significant amount of time and an unwavering commitment. For me, it required dedication, perseverance, and an insatiable desire to tell a story. You have to want to do it, deeply and genuinely. The process may see you sacrificing your evenings and weekends, and sometimes even burning the midnight oil.

The ups and downs of writing

Writing can be a rollercoaster. There are moments when you’re stuck on something, when ideas seem clear in your head but become awkward once written down. The constant back-and-forth, rewriting and revising, can be frustrating.

Yet, it’s a journey filled with discovery and personal growth. As you wrestle with your words and phrases, you learn, improve, and eventually shape your raw thoughts into articulate, compelling prose.

The Joy of Completion

Despite the ups and downs, the feeling of holding your completed book—the tangible fruit of your labour—is incomparable. In the end, once you hold your ‘baby’ in your hands, it’s beautiful.

The joy and satisfaction you derive from seeing your ideas transformed into a book wash away the memory of all previous hardships. It’s an experience akin to the journey of parenthood. Yes, it’s hard and challenging, but the outcome makes you forget all about the struggles.

About Effective Agile

Ralph Jocham is a Change Agent in Scrum // Agile // Coaching // Evidence Based Management and also a Professional Scrum Trainer based in Europe.

As one of the first Professional Scrum Trainers in the world, Ralph has worked directly with cocreator of #scrum, Ken Schwaber, and has played an integral part in the course development of the #PSPO (Professional Scrum Product Owner) as well as the delivery of all #scrum.org certified courses.

If you’re looking to invest in training that transforms and empowers teams to successfully adopt #scrum or #agile, and create high-performance #productdevelopment environments leveraging the agile values and principles, visit https://effectiveagile.com/agile-scru...

If you would like to work with Ralph and company as an #agilecoach, #agileconsultant, or powerful change agent to get your team back on track and on the road to high-performance #agile #productdevelopment, visit https://effectiveagile.com/agile-tran...

For more great ‘how-to’ videos, blogs, and insights, subscribe to this channel and visit https://effectiveagile.com/blog/ for more valuable content.

#scrum #agile #scrumorg #scrumcertification #scrumcourses #scrumtraining #agilescrumtraining #agilekata #agility #businessagility #agileprojectmanagement #projectmanagement #productdevelopment #agileproductdevelopment #switzerland #germany #europe #scrumteam #scrumframework #professionalscrumtrainer #PST #certifiedscrumtrainer #certifiedscrumtraining

What is Conway’s Law?

There’s an adage in software engineering, Conway’s Law, which carries significant implications for the way we structure our organisations and design our software.

Conway’s Law states that any organisation that designs a system will invariably produce a design that mirrors the organisation’s communication structure. To put it in simple terms, the way we interact and communicate within our organisations directly shapes the systems we create.

Its relevance in product development

As a seasoned professional in software engineering and product development, I find Conway’s Law to be particularly relevant. In many companies, we find distinct departments such as databases, architecture, user interfaces, and more. The resulting underlying architecture tends to mimic these divisions or ‘silos’, reflecting their existence within the organisation.

This siloed design, however, poses a significant challenge. The software we create should ideally function as a cohesive, integrated whole. But with distinct elements like database design and business logic existing in separate silos, we encounter numerous interdependencies.

Interdependencies are problematic for several reasons:They amplify the need for communication and synchronisation between different departments.They consume considerable time, which could be better used in productive activities.They are highly susceptible to errors.They give rise to other associated issues that can hamper the overall efficiency and effectiveness of the system.The importance of organisational structure

Given the above, how should we structure our organisations to optimise the process? This is a field I have spent significant time researching, and my findings challenge conventional wisdom and the classical thinking we often see. But that is a post for another day!

For today, remember that Conway’s Law highlights how our organisational structures dictate the systems we design. So go ahead and foster a culture that promotes effective communication, collaboration and the breaking down of silos within your organisations.

About Effective Agile

Ralph Jocham is a Change Agent in Scrum // Agile // Coaching // Evidence Based Management and also a Professional Scrum Trainer based in Europe.

As one of the first Professional Scrum Trainers in the world, Ralph has worked directly with cocreator of #scrum, Ken Schwaber, and has played an integral part in the course development of the #PSPO (Professional Scrum Product Owner) as well as the delivery of all #scrum.org certified courses.

If you’re looking to invest in training that transforms and empowers teams to successfully adopt #scrum or #agile, and create high-performance #productdevelopment environments leveraging the agile values and principles, visit https://effectiveagile.com/agile-scru...

If you would like to work with Ralph and company as an #agilecoach, #agileconsultant, or powerful change agent to get your team back on track and on the road to high-performance #agile #productdevelopment, visit https://effectiveagile.com/agile-tran...

For more great ‘how-to’ videos, blogs, and insights, subscribe to this channel and visit https://effectiveagile.com/blog/ for more valuable content.

#scrum #agile #scrumorg #scrumcertification #scrumcourses #scrumtraining #agilescrumtraining #agilekata #agility #businessagility #agileprojectmanagement #projectmanagement #productdevelopment #agileproductdevelopment #switzerland #germany #europe #scrumteam #scrumframework #professionalscrumtrainer #PST #certifiedscrumtrainer #certifiedscrumtraining