Welcome!

Microservices Expo Authors: Elizabeth White, Pat Romanski, Liz McMillan, Aruna Ravichandran, Carmen Gonzalez

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
When you focus on a journey from up-close, you look at your own technical and cultural history and how you changed it for the benefit of the customer. This was our starting point: too many integration issues, 13 SWP days and very long cycles. It was evident that in this fast-paced industry we could no longer afford this reality. We needed something that would take us beyond reducing the development lifecycles, CI and Agile methodologies. We made a fundamental difference, even changed our culture...
The proper isolation of resources is essential for multi-tenant environments. The traditional approach to isolate resources is, however, rather heavyweight. In his session at 18th Cloud Expo, Igor Drobiazko, co-founder of elastic.io, drew upon his own experience with operating a Docker container-based infrastructure on a large scale and present a lightweight solution for resource isolation using microservices. He also discussed the implementation of microservices in data and application integrat...
Containers have changed the mind of IT in DevOps. They enable developers to work with dev, test, stage and production environments identically. Containers provide the right abstraction for microservices and many cloud platforms have integrated them into deployment pipelines. DevOps and containers together help companies achieve their business goals faster and more effectively. In his session at DevOps Summit, Ruslan Synytsky, CEO and Co-founder of Jelastic, reviewed the current landscape of Dev...
In his General Session at DevOps Summit, Asaf Yigal, Co-Founder & VP of Product at Logz.io, will explore the value of Kibana 4 for log analysis and will give a real live, hands-on tutorial on how to set up Kibana 4 and get the most out of Apache log files. He will examine three use cases: IT operations, business intelligence, and security and compliance. This is a hands-on session that will require participants to bring their own laptops, and we will provide the rest.
"We're bringing out a new application monitoring system to the DevOps space. It manages large enterprise applications that are distributed throughout a node in many enterprises and we manage them as one collective," explained Kevin Barnes, President of eCube Systems, in this SYS-CON.tv interview at DevOps at 18th Cloud Expo, held June 7-9, 2016, at the Javits Center in New York City, NY.
As the race for the presidency heats up, IT leaders would do well to recall the famous catchphrase from Bill Clinton’s successful 1992 campaign against George H. W. Bush: “It’s the economy, stupid.” That catchphrase is important, because IT economics are important. Especially when it comes to cloud. Application performance management (APM) for the cloud may turn out to be as much about those economics as it is about customer experience.
@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...
Updating DevOps to the latest production data slows down your development cycle. Probably it is due to slow, inefficient conventional storage and associated copy data management practices. In his session at @DevOpsSummit at 20th Cloud Expo, Dhiraj Sehgal, in Product and Solution at Tintri, will talk about DevOps and cloud-focused storage to update hundreds of child VMs (different flavors) with updates from a master VM in minutes, saving hours or even days in each development cycle. He will also...
The 20th International Cloud Expo has announced that its Call for Papers is open. Cloud Expo, to be held June 6-8, 2017, at the Javits Center in New York City, brings together Cloud Computing, Big Data, Internet of Things, DevOps, Containers, Microservices and WebRTC to one location. With cloud computing driving a higher percentage of enterprise IT budgets every year, it becomes increasingly important to plant your flag in this fast-expanding business opportunity. Submit your speaking proposal ...
@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.
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...
SYS-CON Events announced today that Super Micro Computer, Inc., a global leader in Embedded and IoT solutions, will exhibit at SYS-CON's 20th International Cloud Expo®, which will take place on June 7-9, 2017, at the Javits Center in New York City, NY. Supermicro (NASDAQ: SMCI), the leading innovator in high-performance, high-efficiency server technology, is a premier provider of advanced server Building Block Solutions® for Data Center, Cloud Computing, Enterprise IT, Hadoop/Big Data, HPC and E...
SYS-CON Events announced today that Linux Academy, the foremost online Linux and cloud training platform and community, will exhibit at 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. Linux Academy was founded on the belief that providing high-quality, in-depth training should be available at an affordable price. Industry leaders in quality training, provided services, and student certification passes, its goal is to c...
The unique combination of Amazon Web Services and Cloud Raxak, a Gartner Cool Vendor in IT Automation, provides a seamless and cost-effective way of securely moving on-premise IT workloads to Amazon Web Services. Any enterprise can now leverage the cloud, manage risk, and maintain continuous security compliance. Forrester's analysis shows that enterprises need automated security to lower security risk and decrease IT operational costs. Through the seamless integration into Amazon Web Services, ...
Software development is a moving target. You have to keep your eye on trends in the tech space that haven’t even happened yet just to stay current. Consider what’s happened with augmented reality (AR) in this year alone. If you said you were working on an AR app in 2015, you might have gotten a lot of blank stares or jokes about Google Glass. Then Pokémon GO happened. Like AR, the trends listed below have been building steam for some time, but they’ll be taking off in surprising new directions b...
A lot of time, resources and energy has been invested over the past few years on de-siloing development and operations. And with good reason. DevOps is enabling organizations to more aggressively increase their digital agility, while at the same time reducing digital costs and risks. But as 2017 approaches, the hottest trends in DevOps aren’t specifically about dev or ops. They’re about testing, security, and metrics.
You often hear the two titles of "DevOps" and "Immutable Infrastructure" used independently. In his session at DevOps Summit, John Willis, Technical Evangelist for Docker, covered the union between the two topics and why this is important. He provided an overview of Immutable Infrastructure then showed how an Immutable Continuous Delivery pipeline can be applied as a best practice for "DevOps." He ended the session with some interesting case study examples.
Software delivery was once specific to the IT industry. Now, Continuous Delivery pipelines are used around world from e-commerce to airline software. Building a software delivery pipeline once involved hours of scripting and manual steps–a process that’s painful, if not impossible, to scale. However Continuous Delivery with Application Release Automation tools offers a scripting-free, automated experience. Continuous Delivery pipelines are immensely powerful for the modern enterprise, boosting ...
Using new techniques of information modeling, indexing, and processing, new cloud-based systems can support cloud-based workloads previously not possible for high-throughput insurance, banking, and case-based applications. In his session at 18th Cloud Expo, John Newton, CTO, Founder and Chairman of Alfresco, described how to scale cloud-based content management repositories to store, manage, and retrieve billions of documents and related information with fast and linear scalability. He addres...
Docker containers have brought great opportunities to shorten the deployment process through continuous integration and the delivery of applications and microservices. This applies equally to enterprise data centers as well as the cloud. In his session at 20th Cloud Expo, Jari Kolehmainen, founder and CTO of Kontena, will discuss solutions and benefits of a deeply integrated deployment pipeline using technologies such as container management platforms, Docker containers, and the drone.io Cl tool...