Welcome!

Microservices Expo Authors: Pat Romanski, Dalibor Siroky, Stackify Blog, Elizabeth White, Liz McMillan

Related Topics: Microservices Expo, Java IoT, Microsoft Cloud, Machine Learning

Microservices Expo: Article

The Agile PMO

Leading the effective, value-driven, Project Management Office

Tom Jenkins, the newly appointed PMO manager convened his team. Xavier, Paula and Xing were eager to start work. Tom explained that the PMO rollout is a change process. He gave his team assignments around stakeholder analysis, mapping of communication requirements, and creation of the PMO newsletter. While the team was somewhat puzzled with these activities they moved to fulfill them. Working with the stakeholders, the team captured many complaints pertaining to the current way of work and gathered numerous requests for improvements. Eagerly awaiting their next meeting, which was held virtually through a videoconference, they prepared a list of proposed improvements. Xavier proposed to commence work on the work breakdown structure and the software development lifecycle. Paula suggested to update the risk register template and to implement a new tool for project scheduling. Xing reported that the stakeholders were keen on having a team collaboration tool and added that they are many resource conflicts which were not managed at present.

Tom listened carefully to his PMO team and empathized with their concerns. He then patiently detailed his vision of the PMO. While this was not the first time he discussed the vision, it was important that the team revisit the vision in light of their findings. He also instructed the team to communicate the vision continuously to the stakeholders during meetings. He further emphasized the importance of communicating through a newsletter to the global community. He moved to investigate with the team, which stakeholders were appearing to be powerful, interested and supportive to the cause of the PMO, and which were appearing to be opposing and would probably produce obstacles to the PMO implementation. He also offered his perspective around which areas may enable quick wins.

He then engaged the team in a discussion about value creation and how the PMO might provide value to the project and product community. He queried the team regarding the current status of the portfolio resource pool. It was evident from the team response that there was a resource pool in existence which was loosely managed, not centrally controlled, and not based on resource planned and actual efforts. Actually, in order to manage the resources on a global basis a new tool had to be implemented and more than 8000 resources had to be updated into the global tool. That was dire news indeed.

It seemed that in order to create value, the newly formed PMO had to immediately invest a huge sum in the procurement and implementation of a new software. Additionally, a new SDLC methodology had to be generated, updated processes had to be written and dozens of templates and work instructions developed.

It seemed a monumental undertaking and the team was at a loss regarding where to begin. They felt that it would be three years before they would start producing value. One of them even suggested hiring a management consulting firm and recruit five additional analysts to help with this huge undertaking. Once more Tom provided support to his team members, permitting them to air out their concerns. Then he explained the concept of the Agile PMO.

100 Days of Grace
He said that they did not have three years to create value; at most they had 100 days of grace before they were expected to produce some initial results. Xavier responded by offering to produce a new version of the risk register which may be not exactly what everyone needed but might make some stakeholders happy and buy the PMO some more precious time.

Tom gently rejected his offer, pointing out that a new risk register while useful, is not what an Agile PMO is about. The new risk register might add confusion and not support value creation and thus would be a waste of effort and time. This led to an extended period of silence and Tom suggested that the team would take a few days to contemplate on how to proceed.

Three days later the team reconvened, Paula proposed an idea. She said that resource conflicts were abundant and that the most value-added activity that the PMO could perform, was to manage resources on a global scale. Tom commented that it was a good idea. Xing questioned the logic of this idea saying, that they are too many resources to manage. Xavier interjected and added that the tool that was in place was not able to support such a task. Paula said that they don’t need to manage all resources, and maybe in an Agile PMO it was enough that they manage only what was needed to enable value creation. The other team members then listened attentively to her idea.

She explained that at this time they do not have a complete list of all projects executed globally and that should be their next task. Once they have such a list they would be able to assess project contribution from a portfolio perspective. Then they would be able to mediate between the different projects and assist management with making educated decisions pertaining to project prioritization based on the full list of projects in the global organization. Tom said that that was a good step in the right direction of being effective.

Eagerly, the team discussed how to carry out mapping of the projects. They defined a template to update the project list into and scheduled a meeting for the following week to review their results. Tom added that it is probably a good idea to present their findings in the newsletter and to continue stakeholders’ assessments regarding support or opposition to the PMO activities.

During the team meeting the week after, it was evident that many pet projects existed, which were using resources without providing benefits to the portfolio. The team mapped about 35% of projects that were redundant and probably unimportant to the portfolio of the company.

Tom said that this was a good example for an Agile PMO. Instead of discussing processes, tools and templates they were engaged in how to make the project and product community more effective. Xing then offered an idea; he said that he had noticed many resource conflicts that were plaguing the projects in his region. He was convinced that these conflicts were occurring between important projects and it was very important to map all the resources allocated to these projects to resolve the conflicts. Resolving the conflicts would enable streamlining important projects, contributing to the portfolio. Xavier said that mapping and allocating all the resources in the region would be impossible as there are more than 800 resources in that specific region, and most of them do not report to timesheets on a regular basis. He added that in any case, the tool in place does not support these reporting requirements. Xing answered that he had given much thought and suggested that initially they map only the critical resources.

The team then deliberated what constitutes a critical resource. Tom offered his perspective and recommended they read an all-time bestseller on the subject of mapping of critical resources by the famous author and physicist Eli Goldratt: “Critical Chain Project Management." He said that true to the concept of the Agile PMO, they will identify critical resources. He estimated that only 3 to 5% of the total number of resources would prove to be critical. By following this line of reasoning, the team would quickly be able to allocate critical resources to prioritized projects enabling streamlining of the value creating projects from the portfolio perspective.

One month later the PMO team was able to provide an almost complete list of projects in the global organization, along with the list of critical resources. These were the critical resources that impacted project completion. By closely managing loading of these resources, the PMO was able to provide and assist project managers and management with timely-based decisions about resource allocations. The PMO also suggested on terminating none value added projects and transferring employees working on these projects to other projects which were creating value from the portfolio perspective. Three months after inception of the PMO, the impact was already tangible:

  1. More stakeholders were moving from neutral attitude to high support of the PMO activities;
  2. The low hanging fruit of critical resource mapping provided quick wins which enabled more rigorous undertakings to complement the initial activities.
  3. The newsletter was instrumental for conveying the message of value creation from the portfolio perspective;

From Push to Pull
With the support of Paula, Xavier and Xing, the vision set forth by Tom became a reality 20 months after PMO inception. Needless to say that within this time the PMO transformed into a strategic tool for portfolio decisions about future projects. The concept of the Agile PMO translated into a PULL mechanism of projects, whereby projects are selected based on resource pool status. This was opposed to the previous approach of a PUSH mechanism whereby all incoming projects were selected, which resulted in the clogging of the resource pool and thus hindering the streamlining effect and reducing the throughput of projects.

Naturally, with time a unified software development lifecycle was constructed along with relevant processes, templates, and then a new software tool for integrating information globally. The software tool was a natural evolution to the development effort of the PMO. The team understood that using a tool to create change is futile, and rather the tool should be implemented after a considerable amount of the change has been in place. The tool as such becomes a method to encapsulate the change into corporate culture.

In conclusion, the Agile PMO delivers what is needed at the time when it is required. The Agile PMO focuses on the most important value creating activities while keeping sight of the overall objective. This is in contrast to the development of all at once, which tends to be the initial expectation that is expressed by stakeholders. The PMO is not about tools, processes, or a methodology, rather it is about creating value.

This article is adapted from chapter nine of the author’s book  The Agile PMO.”

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
While some developers care passionately about how data centers and clouds are architected, for most, it is only the end result that matters. To the majority of companies, technology exists to solve a business problem, and only delivers value when it is solving that problem. 2017 brings the mainstream adoption of containers for production workloads. In his session at 21st Cloud Expo, Ben McCormack, VP of Operations at Evernote, discussed how data centers of the future will be managed, how the p...
The nature of test environments is inherently temporary—you set up an environment, run through an automated test suite, and then tear down the environment. If you can reduce the cycle time for this process down to hours or minutes, then you may be able to cut your test environment budgets considerably. The impact of cloud adoption on test environments is a valuable advancement in both cost savings and agility. The on-demand model takes advantage of public cloud APIs requiring only payment for t...
It has never been a better time to be a developer! Thanks to cloud computing, deploying our applications is much easier than it used to be. How we deploy our apps continues to evolve thanks to cloud hosting, Platform-as-a-Service (PaaS), and now Function-as-a-Service. FaaS is the concept of serverless computing via serverless architectures. Software developers can leverage this to deploy an individual "function", action, or piece of business logic. They are expected to start within milliseconds...
As DevOps methodologies expand their reach across the enterprise, organizations face the daunting challenge of adapting related cloud strategies to ensure optimal alignment, from managing complexity to ensuring proper governance. How can culture, automation, legacy apps and even budget be reexamined to enable this ongoing shift within the modern software factory? In her Day 2 Keynote at @DevOpsSummit at 21st Cloud Expo, Aruna Ravichandran, VP, DevOps Solutions Marketing, CA Technologies, was jo...
You know you need the cloud, but you’re hesitant to simply dump everything at Amazon since you know that not all workloads are suitable for cloud. You know that you want the kind of ease of use and scalability that you get with public cloud, but your applications are architected in a way that makes the public cloud a non-starter. You’re looking at private cloud solutions based on hyperconverged infrastructure, but you’re concerned with the limits inherent in those technologies.
Is advanced scheduling in Kubernetes achievable?Yes, however, how do you properly accommodate every real-life scenario that a Kubernetes user might encounter? How do you leverage advanced scheduling techniques to shape and describe each scenario in easy-to-use rules and configurations? In his session at @DevOpsSummit at 21st Cloud Expo, Oleg Chunikhin, CTO at Kublr, answered these questions and demonstrated techniques for implementing advanced scheduling. For example, using spot instances and co...
The cloud era has reached the stage where it is no longer a question of whether a company should migrate, but when. Enterprises have embraced the outsourcing of where their various applications are stored and who manages them, saving significant investment along the way. Plus, the cloud has become a defining competitive edge. Companies that fail to successfully adapt risk failure. The media, of course, continues to extol the virtues of the cloud, including how easy it is to get there. Migrating...
For DevOps teams, the concepts behind service-oriented architecture (SOA) are nothing new. A style of software design initially made popular in the 1990s, SOA was an alternative to a monolithic application; essentially a collection of coarse-grained components that communicated with each other. Communication would involve either simple data passing or two or more services coordinating some activity. SOA served as a valid approach to solving many architectural problems faced by businesses, as app...
Some journey to cloud on a mission, others, a deadline. Change management is useful when migrating to public, private or hybrid cloud environments in either case. For most, stakeholder engagement peaks during the planning and post migration phases of a project. Legacy engagements are fairly direct: projects follow a linear progression of activities (the “waterfall” approach) – change managers and application coders work from the same functional and technical requirements. Enablement and develo...
Gone are the days when application development was the daunting task of the highly skilled developers backed with strong IT skills, low code application development has democratized app development and empowered a new generation of citizen developers. There was a time when app development was in the domain of people with complex coding and technical skills. We called these people by various names like programmers, coders, techies, and they usually worked in a world oblivious of the everyday pri...
From manual human effort the world is slowly paving its way to a new space where most process are getting replaced with tools and systems to improve efficiency and bring down operational costs. Automation is the next big thing and low code platforms are fueling it in a significant way. The Automation era is here. We are in the fast pace of replacing manual human efforts with machines and processes. In the world of Information Technology too, we are linking disparate systems, softwares and tool...
DevOps is good for organizations. According to the soon to be released State of DevOps Report high-performing IT organizations are 2X more likely to exceed profitability, market share, and productivity goals. But how do they do it? How do they use DevOps to drive value and differentiate their companies? We recently sat down with Nicole Forsgren, CEO and Chief Scientist at DORA (DevOps Research and Assessment) and lead investigator for the State of DevOps Report, to discuss the role of measure...
DevOps is under attack because developers don’t want to mess with infrastructure. They will happily own their code into production, but want to use platforms instead of raw automation. That’s changing the landscape that we understand as DevOps with both architecture concepts (CloudNative) and process redefinition (SRE). Rob Hirschfeld’s recent work in Kubernetes operations has led to the conclusion that containers and related platforms have changed the way we should be thinking about DevOps and...
"As we've gone out into the public cloud we've seen that over time we may have lost a few things - we've lost control, we've given up cost to a certain extent, and then security, flexibility," explained Steve Conner, VP of Sales at Cloudistics,in this SYS-CON.tv interview at 20th Cloud Expo, held June 6-8, 2017, at the Javits Center in New York City, NY.
These days, APIs have become an integral part of the digital transformation journey for all enterprises. Every digital innovation story is connected to APIs . But have you ever pondered over to know what are the source of these APIs? Let me explain - APIs sources can be varied, internal or external, solving different purposes, but mostly categorized into the following two categories. Data lakes is a term used to represent disconnected but relevant data that are used by various business units wit...
With continuous delivery (CD) almost always in the spotlight, continuous integration (CI) is often left out in the cold. Indeed, it's been in use for so long and so widely, we often take the model for granted. So what is CI and how can you make the most of it? This blog is intended to answer those questions. Before we step into examining CI, we need to look back. Software developers often work in small teams and modularity, and need to integrate their changes with the rest of the project code b...
"I focus on what we are calling CAST Highlight, which is our SaaS application portfolio analysis tool. It is an extremely lightweight tool that can integrate with pretty much any build process right now," explained Andrew Siegmund, Application Migration Specialist for CAST, in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
"Cloud4U builds software services that help people build DevOps platforms for cloud-based software and using our platform people can draw a picture of the system, network, software," explained Kihyeon Kim, CEO and Head of R&D at Cloud4U, in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
Kubernetes is an open source system for automating deployment, scaling, and management of containerized applications. Kubernetes was originally built by Google, leveraging years of experience with managing container workloads, and is now a Cloud Native Compute Foundation (CNCF) project. Kubernetes has been widely adopted by the community, supported on all major public and private cloud providers, and is gaining rapid adoption in enterprises. However, Kubernetes may seem intimidating and complex ...
DevOps is often described as a combination of technology and culture. Without both, DevOps isn't complete. However, applying the culture to outdated technology is a recipe for disaster; as response times grow and connections between teams are delayed by technology, the culture will die. A Nutanix Enterprise Cloud has many benefits that provide the needed base for a true DevOps paradigm. In their Day 3 Keynote at 20th Cloud Expo, Chris Brown, a Solutions Marketing Manager at Nutanix, and Mark Lav...