Welcome!

Microservices Expo Authors: Gerardo A Dada, Liz McMillan, Carmen Gonzalez, Elizabeth White, Pat Romanski

Related Topics: Microservices Expo, Java IoT, Linux Containers, Open Source Cloud

Microservices Expo: Article

Agile 101: Product Owner - Improved Insight into Customer Needs

Scrum Agile Leadership and communication skills for Product Owner

In a Scrum-Agile project management environment, the product owner acts as a catalyst of change in the organization, enabling value creation through projects and products. Product owners create the required link between how the business would look like in the future and the current state. The product owner is a key facilitator within the organization in bridging the client and the business community with the Agile development team.

Most of what a product owner performs can be defined in the broader sense as: 1) Creating and increasing value for the business, and 2) Eliminating and reducing costs for the business.

The product owner is required to identify business needs and determine solutions to business challenges. We can characterize the role description of the product owner as related to the above tasks into several key responsibilities. The product owner needs to:

  1. Mine for and create epics that guide the business towards value creation and cost savings;
  2. Plan and maintain epics, themes and user stories;
  3. Elicit epics, themes and user stories;
  4. Reach consensus and understanding of epics themes and user stories between the business and the Agile development team;
  5. Focus on user stories according to specific guidelines such as INVEST (Independent, Negotiable, Valuable, Estimable, Small, Testable);
  6. Communicate and collaborate continuously.

As the product owner is the focal point for strategic and tactical product management, he or she collaborates with many stakeholders and must communicate with all of them. Specifically the product owner interacts with the business community and the Agile development teams on a regular basis. He or she should also communicate with management in making sure that business objectives are indeed captured in themes and epics.

On any single Agile development effort the product owner:

  1. Elicits user stories, making them INVESTabile;
  2. Analyzes them with the team;
  3. Provides feedback to the business community;
  4. Communicates continuously while prioritizing user stories;
  5. Monitors user stories to their respective epics and themes;
  6. Supports the Agile development teams throughout the Sprint - providing clarifications where needed;
  7. Approves and accepts the developed features at the end of the Sprint;
  8. Maintains a rudimentary or full-fledged traceability of user stories to business, to epics and themes, and to any other relevant criteria that he has defined.

Communication is a key differentiator in the product owner's effectiveness and most often an aspect in which product owners are lacking the necessary know how. This, in turn, impacts negatively the product owner's performance. Emphasis is given to the elicitation of user stories since product owners are usually gathering the stories instead of eliciting them.

The main difference between gathering and eliciting is: Elicitation is an analytical, free-flowing communication and collaboration effort which fits well with Agile development as described in the Agile Manifesto. Gathering is a passive activity with little invested analysis. When a product owner is a gatherer he is actually no more than an administrator.

To summarize the points above: it is vital that the product owner understands the context in which he is working, the tools that she can use while performing the work, and the essence of what it means to be a product owner in an effective Agile product development environment.

Improved Insight into Customer Needs

The product owner constantly communicates and collaborates both with the business community and with Agile development teams. Communicating is the basis for collaborating. Communicating has several goals:

  1. Letting others know of something;
  2. Asking for feedback from others;
  3. Convincing others;
  4. Proactively building relationships.

In the process of communication, personal, cultural, intercultural, and language barriers exist. The product owner should be cognizant of these barriers and understand that the same message can be perceived differently than anticipated as well as differently by various groups and teams of stakeholders. An effective product owner understands that messages are received, deciphered and perceived differently by others since they have individual and distinct perception filters. Examples of filter categories can be:

  1. Values-personal - values impact the way a message is perceived;
  2. Interests -  a specific team member interest in a certain user story can impact the way he estimates that story;
  3. Expectations -  different expectations result in different levels of collaboration;
  4. Past experience - past experience can alter how people accept a certain message and respond to it. This for example can result in different understanding of the same user story to be developed.

When communicating we are subjective, moving away from messages that conflict with our ideas and beliefs. We tend to hear just what we want to hear, and we usually pay more attention to things that interest us. Our past experience impact and biases us, emotions and psychological states impact how we perceive a message and how we communicate. Taking into account these obstacles to mutually effective communication, it is vital that the product owner spend time both when eliciting the user stories and also in conveying them to the team. During the Sprint planning meeting or for that matter any other Agile process which includes detailing the user stories to the development team, care should be given to feedback loops and the clear understanding of what is required to be developed.

When discussing the user story with the Agile development team, for example, it is not sufficient to read out loud the user story cards. The product owner should actively ask for feedback to assure understanding concerning the specific story.It is useful to add graphics, diagrams, illustrations and mind maps to emphasize the understanding.

I probably cannot emphasize enough how important this is in an Agile environments. Since Agile is scarce in formal documentation the clear and concise understanding of what is required to be developed during the collaborative process between product owner and the Agile development team, is key to the Agile development process. Without the clear understanding of what needs to be developed, the team might be investing efforts in the wrong direction. Thus, it can be a very efficient Sprint - speedy and producing the stated results; however it will also be an ineffective Sprint - the results received are not the ones that were required.

This constant feedback and communication loop between the product owner and the business community, and between the product owner and the development team, is key to successful product development in Agile environment. It is also a key element in any product development environment; however, as mentioned before, the typical lack of formal documents in Agile necessitates the constant communication and collaboration, clarifying expectations and interests during Agile development.

I suggest that all product owners participate in communication skills training, learn strategies in developing their skills and enhance their facilitation techniques. A practical approach to handle the communication barriers is to make sure that:

  1. One knows the communication objective ahead of time;
  2. Remains cognizant during a communication interaction and analyze the specific situation from both the communicator and the receiver perspectives.
  3. Remains aware of the restrictions imposed by the environment.
  4. Establishes and promotes a multi-way feedback loop;
  5. Is able to communicate in more than one method: i.e. pictures, drawing, diagrams and prototypes. These are great tools to enhance communication.

The product owner's core competencies are facilitation, communication and leadership skills. Effective product owners are able to:

  1. Listen
  2. Emphasize
  3. Facilitate meetings
  4. Handle tough communication and conflict management situations
  5. Be effective presenters
  6. Lead product related business decisions and openly discuss them with the Agile development team
  7. Negotiate, mediate and influence between the Agile development teams and the business community.

Agile Product Owner Michael Amazon

This article is excerpted from the author’s new e-book Agile Product Owner Secrets. A print version of the book is found here

More Stories By Michael Nir

Michael Nir - President of Sapir Consulting - (M.Sc. Engineering) has been providing operational, organizational and management consulting and training for over 15 years. He is passionate about Gestalt theory and practice, which complements his engineering background and contributes to his understanding of individual and team dynamics in business. Michael authored 8 Bestsellers in the fields of Influencing, Agile, Teams, Leadership and others. Michael's experience includes significant expertise in the telecoms, hi-tech, software development, R&D environments and petrochemical & infrastructure industries. He develops creative and innovative solutions in project and product management, process improvement, leadership, and team building programs. Michael's professional background is analytical and technical; however, he has a keen interest in human interactions and behaviors. He holds two engineering degrees from the prestigious Technion Institute of Technology: a Bachelor of civil engineering and Masters of Industrial engineering. He has balanced his technical side with the extensive study and practice of Gestalt Therapy and "Instrumental Enrichment," a philosophy of mediated learning. In his consulting and training engagements, Michael combines both the analytical and technical world with his focus on people, delivering unique and meaningful solutions, and addressing whole systems.

@MicroservicesExpo Stories
Today’s IT environments are increasingly heterogeneous, with Linux, Java, Oracle and MySQL considered nearly as common as traditional Windows environments. In many cases, these platforms have been integrated into an organization’s Windows-based IT department by way of an acquisition of a company that leverages one of those platforms. In other cases, the applications may have been part of the IT department for years, but managed by a separate department or singular administrator. Still, whether...
"Dice has been around for the last 20 years. We have been helping tech professionals find new jobs and career opportunities," explained Manish Dixit, VP of Product and Engineering at Dice, in this SYS-CON.tv interview at 19th Cloud Expo, held November 1-3, 2016, at the Santa Clara Convention Center in Santa Clara, CA.
@DevOpsSummit taking place June 6-8, 2017 at Javits Center, New York City, is co-located with the 20th International Cloud Expo and will feature technical sessions from a rock star conference faculty and the leading industry players in the world. @DevOpsSummit at Cloud Expo New York Call for Papers is now open.
Rapid innovation, changing business landscapes, and new IT demands force businesses to make changes quickly. In the eyes of many, containers are at the brink of becoming a pervasive technology in enterprise IT to accelerate application delivery. In this presentation, attendees learned about the: The transformation of IT to a DevOps, microservices, and container-based architecture What are containers and how DevOps practices can operate in a container-based environment A demonstration of how ...
Cloud Expo, Inc. has announced today that Andi Mann returns to 'DevOps at Cloud Expo 2017' as Conference Chair The @DevOpsSummit at Cloud Expo will take place on June 6-8, 2017, at the Javits Center in New York City, NY. "DevOps is set to be one of the most profound disruptions to hit IT in decades," said Andi Mann. "It is a natural extension of cloud computing, and I have seen both firsthand and in independent research the fantastic results DevOps delivers. So I am excited to help the great t...
Without lifecycle traceability and visibility across the tool chain, stakeholders from Planning-to-Ops have limited insight and answers to who, what, when, why and how across the DevOps lifecycle. This impacts the ability to deliver high quality software at the needed velocity to drive positive business outcomes. In his general session at @DevOpsSummit at 19th Cloud Expo, Phil Hombledal, Solution Architect at CollabNet, discussed how customers are able to achieve a level of transparency that e...
Get deep visibility into the performance of your databases and expert advice for performance optimization and tuning. You can't get application performance without database performance. Give everyone on the team a comprehensive view of how every aspect of the system affects performance across SQL database operations, host server and OS, virtualization resources and storage I/O. Quickly find bottlenecks and troubleshoot complex problems.
Application transformation and DevOps practices are two sides of the same coin. Enterprises that want to capture value faster, need to deliver value faster – time value of money principle. To do that enterprises need to build cloud-native apps as microservices by empowering teams to build, ship, and run in production. In his session at @DevOpsSummit at 19th Cloud Expo, Neil Gehani, senior product manager at HPE, discussed what every business should plan for how to structure their teams to delive...
DevOps is being widely accepted (if not fully adopted) as essential in enterprise IT. But as Enterprise DevOps gains maturity, expands scope, and increases velocity, the need for data-driven decisions across teams becomes more acute. DevOps teams in any modern business must wrangle the ‘digital exhaust’ from the delivery toolchain, "pervasive" and "cognitive" computing, APIs and services, mobile devices and applications, the Internet of Things, and now even blockchain. In this power panel at @...
SYS-CON Events announced today that Dataloop.IO, an innovator in cloud IT-monitoring whose products help organizations save time and money, has been named “Bronze Sponsor” of SYS-CON's 20th International Cloud Expo®, which will take place on June 6-8, 2017, at the Javits Center in New York City, NY. Dataloop.IO is an emerging software company on the cutting edge of major IT-infrastructure trends including cloud computing and microservices. The company, founded in the UK but now based in San Fran...
@DevOpsSummit at Cloud taking place June 6-8, 2017, at Javits Center, New York City, is co-located with the 20th International Cloud Expo and will feature technical sessions from a rock star conference faculty and the leading industry players in the world. The widespread success of cloud computing is driving the DevOps revolution in enterprise IT. Now as never before, development teams must communicate and collaborate in a dynamic, 24/7/365 environment. There is no time to wait for long developm...
As we enter the final week before the 19th International Cloud Expo | @ThingsExpo in Santa Clara, CA, it's time for me to reflect on six big topics that will be important during the show. Hybrid Cloud: This general-purpose term seems to provide a comfort zone for many enterprise IT managers. It sounds reassuring to be able to work with one of the major public-cloud providers like AWS or Microsoft Azure while still maintaining an on-site presence.
I’m a huge fan of open source DevOps tools. I’m also a huge fan of scaling open source tools for the enterprise. But having talked with my fair share of companies over the years, one important thing I’ve learned is that you can’t scale your release process using open source tools alone. They simply require too much scripting and maintenance when used that way. Scripting may be fine for smaller organizations, but it’s not ok in an enterprise environment that includes many independent teams and to...
Between 2005 and 2020, data volumes will grow by a factor of 300 – enough data to stack CDs from the earth to the moon 162 times. This has come to be known as the ‘big data’ phenomenon. Unfortunately, traditional approaches to handling, storing and analyzing data aren’t adequate at this scale: they’re too costly, slow and physically cumbersome to keep up. Fortunately, in response a new breed of technology has emerged that is cheaper, faster and more scalable. Yet, in meeting these new needs they...
More and more companies are looking to microservices as an architectural pattern for breaking apart applications into more manageable pieces so that agile teams can deliver new features quicker and more effectively. What this pattern has done more than anything to date is spark organizational transformations, setting the foundation for future application development. In practice, however, there are a number of considerations to make that go beyond simply “build, ship, and run,” which changes how...
In his general session at 19th Cloud Expo, Manish Dixit, VP of Product and Engineering at Dice, discussed how Dice leverages data insights and tools to help both tech professionals and recruiters better understand how skills relate to each other and which skills are in high demand using interactive visualizations and salary indicator tools to maximize earning potential. Manish Dixit is VP of Product and Engineering at Dice. As the leader of the Product, Engineering and Data Sciences team at D...
SYS-CON Events has announced today that Roger Strukhoff has been named conference chair of Cloud Expo and @ThingsExpo 2017 New York. The 20th Cloud Expo and 7th @ThingsExpo will take place on June 6-8, 2017, at the Javits Center in New York City, NY. "The Internet of Things brings trillions of dollars of opportunity to developers and enterprise IT, no matter how you measure it," stated Roger Strukhoff. "More importantly, it leverages the power of devices and the Internet to enable us all to im...
In IT, we sometimes coin terms for things before we know exactly what they are and how they’ll be used. The resulting terms may capture a common set of aspirations and goals – as “cloud” did broadly for on-demand, self-service, and flexible computing. But such a term can also lump together diverse and even competing practices, technologies, and priorities to the point where important distinctions are glossed over and lost.
Monitoring of Docker environments is challenging. Why? Because each container typically runs a single process, has its own environment, utilizes virtual networks, or has various methods of managing storage. Traditional monitoring solutions take metrics from each server and applications they run. These servers and applications running on them are typically very static, with very long uptimes. Docker deployments are different: a set of containers may run many applications, all sharing the resource...
Logs are continuous digital records of events generated by all components of your software stack – and they’re everywhere – your networks, servers, applications, containers and cloud infrastructure just to name a few. The data logs provide are like an X-ray for your IT infrastructure. Without logs, this lack of visibility creates operational challenges for managing modern applications that drive today’s digital businesses.