The Product Owner in our Leadership Team Part III

We have been discussing the Product Owner position in detail this past week. This position is a key part of our leadership team that we are currently recruiting. If you have an interest in the Product Owner position for one of our modules or technologies please contact me below. In the last post we discussed the Leader and Team Player attributes of the position. Today we continue with several other attributes of the Product Owner. Quotations are from the book “Agile Product Management with Scrum: Creating Products that Customers Love” by Roman Pichler.

People, Ideas & Objects state that we are filling a “gap” between the oil and gas, and Information Technology industries. Creating a sub-industry where nothing exists today. This “gap” exists as the technologies have become too specialized and as a result technology firms are unable to fully understand the needs of its customers, the oil and gas firms. What we are doing in filling this “gap” is providing a means of communication between the oil and gas and Information Technology industries so that they operate more effectively. In the book Roman Pichler states that the Product Owner is an effective communicator and negotiator that operates to “communicate with and aligns different parties, including customers, users, development and engineering, marketing, sales, service, operations, and management. The Product Owner is the voice of the customer, communicating customer needs and requirements and bridging the gap between ‘the suits’ and ‘the techies.’” It is this role as communicator and negotiator that we are placing so much emphasis on the Product Owner role within our leadership team of the user community.

The next two attributes that an effective Product Owner requires are to be empowered and committed. The ability to present new projects for development, and the ability to cancel poorly performing ones are necessary for the continuous improvement of the modules. The Product Owner also needs to have budgetary control of the module they are responsible for. These attributes impute a senior level of responsibility, especially considering the size of the user community budget for each module. Therefore an executive level of commitment is expected in return and as the book states “A successful Product Owner is confident, enthusiastic, energetic, and trustworthy.”

The physical location of the Product Owners matters. Our development team will be based in Houston. Therefore the Product Owners will be based in Houston. The need to have the Product Owners interact with the development team for their individual modules on a regular basis is a necessity. And this requirement would mean a minimum of two days per week. The offices of the Product Owners and user community resources will be located with the development team, therefore this will not be an issue.

Another key role in the development team is what is called the ScrumMaster. “The ScrumMaster supports the Product Owner and the development team, protects the team and the process, and intervenes appropriately when required to ensure that the pace of work is sustainable, that the team stays healthy and motivated, and that no technical debt is incurred.” And “The Product Owner is primarily responsible for the “what” -- creating the right product. The ScrumMaster is primarily responsible for the “how” -- using Scrum the right way. Only when the right product is created with the right process is enduring success achieved.”

The Preliminary Specification and user community provides the oil and gas producer with the most dynamic, innovative and profitable means of oil and gas operations. People, Ideas & Objects Revenue Model specifies the means in which investors can participate in these user defined software developments. Users are welcome to join me here. Together we can begin to meet the future demands for energy. And don't forget to join our network on Twitter @piobiz anyone can contact me at 403-200-2302 or email here. 

The Product Owner in our Leadership Team Part II

Our second installment of the Product Owner positions series begins to look at the desirable characteristics of the individuals in these roles. I will be quoting heavily from the book “Agile Product Management with Scrum: Creating Products that Customers Love” by Roman Pichler. As Product Owners I want them to be the individuals that are responsible for the success of the module that they work with. That their user community is how they achieve that success and they hold our development team to be accountable to the needs of the user community. In order to achieve the oil and gas industry wide software development capability that I think is necessary. One that identifies and overcomes the industries issues and implements its opportunities on a real time basis. I think this is what will be required on a minimum basis.

I have always classified the world into two types of people. Thinkers and doers. I'm a thinker and thankfully there are few of us. The rest are doers. And the book by Roman Pichler says that the Product Owner needs to be a visionary and a doer. I don't think I've personally met anyone with those qualifications but we'll take his word. He defines the Product Owner as an “entrepreneur, the product owner facilitates creativity; encourages innovation; and is comfortable with change, ambiguity, debate, conflict, playfulness, experimentation, and informed risk taking.” All attributes that everyone would encourage.

The next attributes that are highlighted are “Leader and Team Player” and the author has highlighted a phenomenal quotation that I've quoted below.

The Entrepreneurial Team 

We sometimes focus on an individual as the amazing entrepreneur or the outstanding leader -- thinking of Bill Gates, Steve Jobs, and other celebrity leaders. In reality, very few innovations are a stroke of genius attained by one person. And even if the product owner is Mrs. or Mr. Innovation, the individual still needs a team to bring the product to life. No entrepreneurial genius can make all the right decisions. In fact, neuroscientific research reveals that even the best qualified person in the right job at the right place can make wrong decisions -- if that person decides alone. Finkelstein and his coauthors attribute this to the way human cognition works (2009). They recommend using at least one other person as a sounding board. A team provides plenty of sparring partners to test ideas and arrive at the right decision. Ed Catmull, president of Pixar (2008, 68), says this: 

… if you give a mediocre idea to a great team, they will either fix it or throw it away and come up with something that works. 

The wisdom of many is preferable to the brilliance of one.

Which says all there really needs to be said about what we are trying to achieve here at People, Ideas & Objects. The user community is the key to the success of the oil and gas industry in terms of its abilities and capabilities. Software defines and supports organizations. The user community defines the software. Therefore a great team positioned in the user community would be the objective that we should all be pursuing to ensure a successful oil and gas industry. And the Product Owner has an interesting view of these events.

The Preliminary Specification and user community provides the oil and gas producer with the most dynamic, innovative and profitable means of oil and gas operations. People, Ideas & Objects Revenue Model specifies the means in which investors can participate in these user defined software developments. Users are welcome to join me here. Together we can begin to meet the future demands for energy. And don't forget to join our network on Twitter @piobiz anyone can contact me at 403-200-2302 or email here.

The Product Owner in our Leadership Team Part I

Something people have to keep in mind about People, Ideas & Objects is that we are currently in development. By focusing on developing the user community, this is a key part of the software development and the software development capability that we will be providing to the industry. It may seem to the casual reader that things are static at this point, however, as this year develops we will see that this development in the user community will bring about many of the desired outcomes that we anticipate. Stay tuned, I promise this will be an interesting year.

One of the things that we are experiencing is that with the Internet and cloud computing our progress is able to move at the speed at which change is happening. We are not being constrained by the traditional resources of a software developer. Everything is virtual at this point and as a result is able to accommodate the needs of the people we are appealing to and the oil and gas industry. We have a lightweight footprint that is unconstrained by the physical world.

One of our objectives is to recruit the user communities leadership team and have them represent the user community to the oil and gas investors. This was to secure the funding necessary to develop the Preliminary Specification and have the user community and service providers developed. I recently changed my mind on this point. We will continue to recruit these positions, however, we are not going to expose any of these individuals to the antics of the bureaucracies vindictive ways. There is no reason that these people need to take on any career risk by being named here. Therefore from the point of view of what will be expressed to the investors, what you currently see, is what you get.

I am therefore going to begin to detail the specific positions that we are looking to fill in the leadership team and what those positions will be doing. The first position I want to discuss is the Product Owner positions of the user community. We expect that there may be upwards of 20 out of the total of 30 leadership team positions being Product Owners. Starting today I want to begin a discussion of that role and what they provide to the user community, the development team and to the software quality.

The quotations that I will be making are from the book, “Agile Product Management with Scrum: Creating Products that Customers Love” by Roman Pichler. What he suggests as the reason that the Product Owner role exists is to solve the issue of having too many cooks spoiling the soup. Having a single individual leading the development of the product from beginning to end provides this solution. Making one person responsible for ensuring its success and ensuring that everyone involved has a shared vision of the product is the Product Owner role in the development. In the broad scope and scale of the Preliminary Specification I am more or less its Product Owner. But each Product Owner in the leadership team will be either responsible for one module of the Preliminary Specification or some element of the technology. For example the data model, the user interface etc. So for example we will have a very senior individual who will be the Product Owner for the Partnership Accounting Module, and they will have the authority and responsibility for that module.

In the book the Product Owner role is defined as,

The Product Owner is the one and only person responsible for the managing the Product Backlog and ensuring the value of the work the team performs. This person maintains the Product Backlog and ensures that it is visible to everyone. 

If we think for a minute we may have 250 to 300 users in the Partnership Accounting module. This being a simple mathematical representation of the total of 3,000 people in the user population. There may be a need for far more people, especially considering the Material Balance Report which is a critical part of the module. The scope of the module is very broad, however it is consistent in terms of the type of work that is being done and therefore can be handled by one leader or Product Owner. Ensuring that the user community has considered the differences present in the People, Ideas & Objects Preliminary Specification. Having adopted those differences in their input and their analysis of what is required in their systems. It is then the responsibility of the Product Owner to ensure that the development team delivers that product to the user community.

The background of the Product Owners for People, Ideas & Objects purposes is from the business domain. Although a key member of the development team, their understanding of the business domain is what is required. Particularly with respect to the manner in which their understanding of these critical oil and gas processes are handled. It can take years, and sometimes decades before people are fully aware of the total scope of the processes under management in modules such as the Partnership Accounting module. A technological focus is not what we need to ensure product quality or to represent the user community. There will be significant developer and user collaborations and interactions throughout the course of product design and development. And the developers will have time to understand the nuances of the particular parts of the module from individual users, however there is the bigger picture that needs to be captured as well. And from a business perspective, that needs to be provided from the Product Owner.

We'll be discussing the Product Owner position in more detail in the next few days. If you have an interest in these positions, or any of our leadership teams positions please contact me.

The Preliminary Specification and user community provides the oil and gas producer with the most dynamic, innovative and profitable means of oil and gas operations. People, Ideas & Objects Revenue Model specifies the means in which investors can participate in these user defined software developments. Users are welcome to join me here. Together we can begin to meet the future demands for energy. And don't forget to join our network on Twitter @piobiz anyone can contact me at 403-200-2302 or email here. 

Leadership in the User Community

Our discussion has focused on the development of the user community and why that is needed to replace the bureaucracy in the oil and gas industry. What I wanted to talk about today is the first real ingredient of the user community in terms of its needs. And that is leadership. For all intents and purposes the user community is a separate organization that is driven by its own vision, purpose, community and stakeholders. Therefore the leadership is an aspect that needs to be developed from those who commit to the overall vision of the Preliminary Specification and desire to provide the oil and gas producer with the most profitable means of oil and gas operations.

And there will be two types of leadership that make up the user community leadership group. There is the organizational focused leadership group that will be focused on what the needs of the user community are. Secondly there will be the leadership group that provides the continuous leadership in terms of the business model for the oil and gas industry. This will include the twenty or so Product Owners who are responsible for either a specific module of the Preliminary Specification or an element of its development. I think now we begin to see why we have allocated the next five years towards user community developments.

This is the hard work of developing an organization that meets the needs of the software, the industry, the service providers and most importantly the people in the industry. To build an application on Oracle Fusion Middleware and Oracle Fusion Applications can be done by anyone with the money to do so. To add a vision as compelling as the Preliminary Specification to the mix adds a lot of value to the process. However, building a user community to define and support the Oracle and People, Ideas & Objects software will ensure that this environment becomes successful for all concerned. And that is the only manner in which I will continue with this software development project. It would be nice to have the financial resources to spend our way to building the user community. And maybe one day that will happen. But with the bureaucracies attitude towards us that is a non starter. We therefore should look forward to a process of building this user community brick by brick and stick by stick. Based on our capability of providing the oil and gas producer with the most profitable means of oil and gas operations. One day the resources will be there and we can begin these software developments. However we are not in control of that timing at this point so we must do what we can do, and that is organize ourselves for the eventuality of developing the software.

McKinsey Consulting have a good article on the topic of leadership entitled “Change Leader, Change Thyself.” And within it they have an exhibit that I can't reproduce. You can download the article and view the Exhibit for yourself. Its the one that details the roles and responsibilities of the CEO, CFO, COO and Human Resource Officer. Their focus of attention, their source of power and their sweet spot. It is those roles that need to be filled in the user community as an organization in the next five years before we begin development.

Other roles that will need to be filled are the 20 or so product owner roles we mentioned earlier. These are fascinating roles that take a premier seat in the software development team. They are the ultimate representative of the user community for the scope of the teams development authority. So if the team was developing the Partnership Accounting module the Partnership Accounting Product Owner would ensure that the user communities needs were understood and implemented in the software by the People, Ideas & Objects software development team. Having expert knowledge in the area, in this case partnership accounting, the Product Owner is able to interpret the user communities needs and desires and increase the effective communication between the user community and the development team. Ensuring that no misunderstandings or confusion between the groups cause delays or faulty software.

These are just some of the obvious leadership roles that are necessary in the user community. As we proceed in the next five years we will begin to put more elements of what is required and how we expect things to develop. However if you have any comments or concerns don't hesitate to contact me or use the comment feature on this blog.

The Preliminary Specification provides the oil and gas producer with the most profitable means of oil and gas operations. People, Ideas & Objects Revenue Model specifies the means in which investors can participate in these user defined software developments. Users are welcome to join me here. Together we can begin to meet the future demands for energy. And don't forget to join our network on Twitter @piobiz anyone can contact me at 403-200-2302 or email here. 

Hagel & Brown on Leadership

John Hagel and John Seeley Brown are two authors that we follow closely here at People, Ideas & Objects. In a Forbes article entitled “Today You Can Only be a Leader by Creating Leaders” they bring up the topic of leadership and how it’s changing.

In a world where automation of transactions and business processes increases, and escalates, particularly with the development of the Draft Specification, leadership is one of the key human actions and skills that can not be automated. A short list of the types of work that people will be involved in in the future is as follows.

• Leadership
• Issue Identification
• Issue Resolution
• Decisions
• Design
• Ideas
• Search

This is to name just a few of the key human activities that will be needed. When we talk about leadership, we note the size and scope of the task that People, Ideas & Objects is focused on. It is the enormity of this task that will require many leaders. Whether its a Product Owner who will work to capture the users demands in the software, or a member of the Community of Independent Service Providers leading a system integration at a producer firm, leadership will be a key skill that will be needed. Hagel & Brown note the somewhat simple process in which this starts.

Leaders can flip these perceptions of risk and reward if they can paint compelling long-term views of the future. This is completely against the grain for most business and political leaders today; they study quarterly numbers to carefully craft a short-term view of the road ahead. Leaders in the big shift will be those who can peer ahead and paint compelling views of opportunities--and not just opportunities for themselves or their institutions but for all kinds of people. If they can help us to make sense of the long-term future, they'll be able to inspire bold action and investment in support of their initiatives, while everyone else sits on the sidelines.

People interested in getting involved with People, Ideas & Objects should contact me here to begin the process of joining this project. People who are interested in building and providing the systems and services the innovative oil and gas producers will need to meet the market demand for energy. We should also take note of the following.

But there will be another even bigger change in leadership. In the past, leaders were measured by how many people followed them. In the era ahead, they will be measured by how many other leaders they can cultivate. We are moving from a world of push, where people are expected to follow detailed scripts to accomplish specified tasks, to a world of pull, where everyone must master the techniques of drawing out people and resources when needed to address unanticipated opportunities and challenges. In the world of push, followers were prized. In the world of pull, everyone must figure out how to become a leader in their own domain.

This makes intuitive sense. With the systems handling the majority of the business, the remaining tasks are not going to be distributed by some all knowing greater power. The more that can be initiated by the leader, the higher the value that is generated for the producers.

Rather than using persuasion to get others to follow predefined programs, the new generation of leaders will use persuasion to help people more effectively draw out their own individual potential. The really effective leader will be one who can persuade emerging leaders to join forces toward common goals and develop faster than they could on their own.

I can’t think of a more exciting place to work. People, Ideas & Objects, the Community of Independent Service Providers offers leaders a place where their skills are needed.

The bottom line: Leaders will no longer be defined by the number of followers they have, but rather by the number of other leaders they have cultivated and mobilized across institutional boundaries. That is a profound shift.

For the industry to successfully provide for the consumers energy demands, it’s necessary to build the systems that identify and support the Joint Operating Committee. Building the Preliminary Specification is the focus of People, Ideas & Objects. Producers are encouraged to contact me in order to support our Revenue Model and begin their participation in these communities. Those individuals that are interested in joining People, Ideas & Objects can join me here and begin building the software necessary for the successful and innovative oil and gas industry.

Technorati Tags: People's Hagel Brown Leadership CISP Product-Owner

Positions, positions and more positions.

First of all, let me note for the record, we are not in a position to hire anyone. We have no financial support from the industry and expect no one to have to incur any risk in the development of these systems. There are times when writing this blog seems like I have become completely delusional, this is one of those posts. The purpose in mentioning these positions is to provide the readers of this blog with an understanding of where and how they may be able to fit into the developments, when they are funded.

In past blog entries we have been able to list a small number of positions that are involved in the development of the application. These previously noted positions are as follows.

Product Owner

When we begin development, we will be looking for these somewhat new and interesting positions. With the number of development teams approaching the low twenties, each with their own Product Owners, we will be looking for a large number of people to fill these positions.

In a previous blog post, we documented some of the work that is carried out by Product Owners.

Account Manager

A little bit of chaos never hurt anyone. Too much chaos and we run the risk of disrupting the communities involved in this development. That’s what the Account Manager position is designed to deal with. Ideally these people are seconded from the producer firms that they will represent as an Account Manager. In a previous blog post, we documented the work of the Account Manager.

Agile Team Business Analyst

We highlighted the Agile Team Business Analyst position in another recent blog post.

We also have the following executive positions available, when we are funded that is.

Chief Financial Officer

As all good firms have, financial management is an inherent part of success. As someone who has been a CFO, I have a strong perspective on the position. The CFO of any firm has to be the one that is ultimately responsible for the financial success. And they have the power necessary to make this so.

A difficult task of this position will be the compensation provided to the Community of Independent Service Providers. That is to say with so many participants in the development and the CISP, managing the work flow of these communities will be an important aspect of the success of this position.

Chief Operating Officer

Keeping all the balls in the air is the skill that these people provide their firms. COO’s have the ability to anticipate the needs of the organization and prepare the way for the smooth implementation of those capabilities.

Vice-President Development

Heading the software development effort of People, Ideas & Objects will be the responsibility of this position. From managing the “Agile” development team, which is expected to grow to 300 developers, to maintaining the development tools. This position is responsible for anything and everything to do with the software.

Since we are an Oracle customer, this person will need to be well versed in those technologies. Recall that our strategy regarding Oracle is that we use their technologies from stem to stern. It would therefore be incumbent on this position to use the Oracle resources to the utmost. Having a large team of Oracle developers and consultants would therefore be expected to be employed by the Vice-President Development of People, Ideas & Objects.

Vice-President Community Development

Working with the resources as presented by the Community of Independent Service Providers. This person will need to ensure the CISP develops in the best interests of the innovative oil and gas producers. The Account Manager positions noted earlier in this post will also report to the Vice President Community Development. Therefore there will be a large emphasis on policies and procedures to ensure these large populations of people are prepared, motivated and capable of meeting the demands of the innovative producers.

Vice-President Business Development

We are committed to the oil and gas industry as software developers. We are not, and will not entertain the thinking that we can provide service to other industries. With this in mind, the Vice-President Business Development is seen more as a resource that is available to the executive team. Added bench strength in areas of issues and opportunities will serve the firm and the innovative oil and gas producers well.

Vice-President Infrastructure. 

I had previously detailed the hardware policies and procedures of People, Ideas & Objects. The oil and gas industry is expected to provide the individual to head the hardware infrastructure to run the People, Ideas & Objects software applications. This is done to ensure they have the means to have their applications run in a manner that is consistent with their compliance and governance needs.

The president of the hardware firm is also the Vice-President Infrastructure for People, Ideas & Objects. As a member of the team this individual will have to have an intimate understanding of the software and its needs.

Director Research

When you look at the organizational chart in this post. The position of Vice-President of Research is held by myself. The Director Research position therefore needs to be capable of working with me to guide the firm on its long term path.

Members of the Community of Independent Service Providers

And one’s imagination is the only limit to the types of work that can be done as a member of the Community of Independent Service Providers.

One of the attributes of the work at People, Ideas & Objects is the range and scope of understanding. We need to know the business of the oil and gas industry, the advanced hardware and software technologies and the academic sciences of organizational economics as well as other disciplines. A very challenging and rewarding group of positions in these fast paced times.

Society is put in peril when world oil production declines. There is evidence that the world's oil production has declined. Therefore the world needs to have the energy industry expand its production. To do so requires that we reorganize to enhance the division of labor and specialization within the industry. As has been proven, this reorganization could achieve far greater oil and gas production. Management of the industry is conflicted in expanding the output of the industry. The less they do, the higher the oil and gas prices and the better they appear to perform. This managerial conflict must be addressed and the performance of the industry unleashed. To do so requires the current management of the industry to fund People, Ideas & Objects and build the systems as defined in the Draft Specification. Please join me here.

Technorati Tags: People's Business-Analyst Account-Manager Community Product-Owner Organization

Product Owner - Position

The Agile / Scrum software development methodology has many predefined roles. The Product Owner is one of them, and Product Owners are a part of the Scrum team. People, Ideas & Objects will have many Product Owners. One for each of 20 possible Scrum teams. [Eleven defined modules of the Draft Specification, User-Interface, Architecture, Data model etc.]

Project Owners are "pigs" in the scrum world. Pigs, unlike Chickens, have everything invested at the breakfast table. An appropriate term in my opinion. Their job is simple, satisfy all stakeholder concerns. Working with the many Account Managers of producers and their users, the Community of Independent Service Providers, (CISP) and their Scrum Team members. Product Owners will be the individuals who magically prioritize the developments to meet the changing needs of the producers.

By adopting Oracle technologies People, Ideas & Objects inherits their entire technology stack. An Open yet integrated technology stack like no other. Making the Draft Specification and subsequent designs executable is no small task, we are grateful for the vision and execution of Oracle Hardware & Software. We are also constrained by those technologies, and it will be the Product Owners that feel those constraints the most.

By adopting Oracle we will have an advanced tool set and infrastructure to deal with. Our developers and particularly our Product Owners will have to be intimately familiar with Oracle technologies. This is the standard means of Oracle application delivery in the marketplace. There is a substantial marketplace of Oracle consultants available to People, Ideas & Objects and associated communities. In addition to the need to be familiar with the Oracle technology stack, Product Owners will need to be intimately familiar with the oil and gas industry, generic business needs and their "products". I'm just glad I already have a job at People, Ideas & Objects.

By way of a scenario, as the Product Owner of the Petroleum Lease Marketplace (PLM) Module a day might look similar to this... The Product Owner reviews a small sample of email messages, and prior days edits to the wiki. Edits and comments from the 500 Account Managers and 27,000 users who use the PLM. Account Managers are at times representative of the collective desires of these 27,000 users. These users have compiled a wish list of 1,000 user stories of what they need and want in the PLM software. Although daunting, the solutions to each can be represented by making 15 major changes in the PLM. The Product Owner has been blogging about these 15 proposed changes, for a number of weeks. These changes are also passionately felt by many of the members in the CISP. As always, major changes in the software can be brought into production with one two-week sprint. The Project Owner has recruited a representative group of users from 12 producers to work with the developers during that sprint. The Product Owner sets tomorrow for the team to begin these developments. Suddenly she realizes it's 7:30 in the morning and she has to get ready to catch a flight to Europe for the bi-annual People, Ideas & Objects user conference...

A little creative license is handy. If your an enlightened producer, an oil and gas investor or shareholder, who would be interested in funding these software developments and communities, please follow our Funding Policies & Procedures, and our Hardware Policies & Procedures. If your a government that collects royalties from oil and gas producers, and are concerned about the accuracy of your royalty income, please review our Royalty Policies & Procedures and email me. And if your a potential user of this software, and possibly as a member of the Community of Independent Service Providers, please join us here.

Technorati Tags: People's Project-Owner Passion Oracle PLM Development CISP Agile-Scrum