|By Michael Nir||
|December 5, 2013 11:55 AM EST||
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:
- More stakeholders were moving from neutral attitude to high support of the PMO activities;
- The low hanging fruit of critical resource mapping provided quick wins which enabled more rigorous undertakings to complement the initial activities.
- 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.
Naturally, new and exciting technologies and trends like software defined networking, the Internet of Things and the cloud tend to get the lion’s share of attention these days, including when it comes to security. However, it’s important to never forget that at the center of it all is still the enterprise network. And as evidenced by the ever-expanding landslide of data breaches that could have been prevented or at least their impact lessened by better practicing network security basics, it’s ...
Dec. 2, 2015 01:45 AM EST Reads: 308
Put the word continuous in front of many things and we help define DevOps: continuous delivery, continuous testing, continuous assessment, and there is more. The next BriefingsDirect DevOps thought leadership discussion explores the concept of continuous processes around the development and deployment of applications and systems. Put the word continuous in front of many things and we help define DevOps: continuous delivery, continuous testing, continuous assessment, and there is more.
Dec. 2, 2015 01:30 AM EST Reads: 204
This morning on #c9d9 we spoke with two industry veterans and published authors - James DeLuccia and Jonathan McAllister - on how to bake-in security and compliance into your DevOps processes, and how DevOps and automation can essentially help you pass your next audit.
Dec. 2, 2015 01:30 AM EST Reads: 136
Hiring the wrong candidate can cost a company hundreds of thousands of dollars, and result in lost profit and productivity during the search for a replacement. In fact, the Harvard Business Review has found that as much as 80 percent of turnover is caused by bad hiring decisions. But when your organization has implemented DevOps, the job is about more than just technical chops. It’s also about core behaviors: how they work with others, how they make decisions, and how those decisions translate t...
Dec. 2, 2015 12:45 AM EST Reads: 233
In today’s pharmaceutical supply chain, counterfeit activity is thriving. As pharma companies have expanded target markets and outsourced production over the last decade, the supply chain has become increasingly global, virtual, and vulnerable. Illicit activity has thrived, and patients have suffered, with hundreds of thousands dying each year from counterfeit and contaminated drugs. More than 40 countries have responded with new laws that regulate prescription medications as they travel throug...
Dec. 1, 2015 11:45 PM EST Reads: 332
In his General Session at DevOps Summit, Asaf Yigal, Co-Founder & VP of Product at Logz.io, explored the value of Kibana 4 for log analysis and provided a hands-on tutorial on how to set up Kibana 4 and get the most out of Apache log files. He examined three use cases: IT operations, business intelligence, and security and compliance. Asaf Yigal is co-founder and VP of Product at log analytics software company Logz.io. In the past, he was co-founder of social-trading platform Currensee, which...
Dec. 1, 2015 11:00 PM EST Reads: 307
SYS-CON Events announced today that Catchpoint, a global leader in monitoring, and testing the performance of online applications, has been named "Silver Sponsor" of DevOps Summit New York, which will take place on June 7-9, 2016 at the Javits Center in New York City. Catchpoint radically transforms the way businesses manage, monitor, and test the performance of online applications. Truly understand and improve user experience with clear visibility into complex, distributed online systems.Founde...
Dec. 1, 2015 10:15 PM EST Reads: 140
People want to get going with DevOps or Continuous Delivery, but need a place to start. Others are already on their way, but need some validation of their choices. A few months ago, I published the first volume of DevOps and Continuous Delivery reference architectures which has now been viewed over 50,000 times on SlideShare (it's free to download...no registration required). Three things helped people in the deck: (1) the reference architectures, (2) links to the sources for each architectur...
Dec. 1, 2015 09:30 PM EST Reads: 292
The Internet of Things (IoT) is growing rapidly by extending current technologies, products and networks. By 2020, Cisco estimates there will be 50 billion connected devices. Gartner has forecast revenues of over $300 billion, just to IoT suppliers. Now is the time to figure out how you’ll make money – not just create innovative products. With hundreds of new products and companies jumping into the IoT fray every month, there’s no shortage of innovation. Despite this, McKinsey/VisionMobile data...
Dec. 1, 2015 04:00 PM EST Reads: 507
Cloud computing is unquestionably one of the driving forces of DevOps, as the automation of operations transforms enterprise software development. DevOps, however, is more than a technology trend, as it represents a move toward silo-busting, self-organizing horizontal teams that drive business velocity. At the same time, enterprise Digital Transformation represents an upheaval across the enterprise, as customer preferences and behavior drive enterprise technology decisions. This transformation ...
Dec. 1, 2015 03:45 PM EST
Most of the IoT Gateway scenarios involve collecting data from machines/processing and pushing data upstream to cloud for further analytics. The gateway hardware varies from Raspberry Pi to Industrial PCs. The document states the process of allowing deploying polyglot data pipelining software with the clear notion of supporting immutability. In his session at @ThingsExpo, Shashank Jain, a development architect for SAP Labs, discussed the objective, which is to automate the IoT deployment proces...
Dec. 1, 2015 03:00 PM EST Reads: 152
One of the most important tenets of digital transformation is that it’s customer-driven. In fact, the only reason technology is involved at all is because today’s customers demand technology-based interactions with the companies they do business with. It’s no surprise, therefore, that we at Intellyx agree with Patrick Maes, CTO, ANZ Bank, when he said, “the fundamental element in digital transformation is extreme customer centricity.” So true – but note the insightful twist that Maes adde...
Dec. 1, 2015 03:00 PM EST Reads: 479
Just over a week ago I received a long and loud sustained applause for a presentation I delivered at this year’s Cloud Expo in Santa Clara. I was extremely pleased with the turnout and had some very good conversations with many of the attendees. Over the next few days I had many more meaningful conversations and was not only happy with the results but also learned a few new things. Here is everything I learned in those three days distilled into three short points.
Dec. 1, 2015 03:00 PM EST Reads: 389
DevOps is about increasing efficiency, but nothing is more inefficient than building the same application twice. However, this is a routine occurrence with enterprise applications that need both a rich desktop web interface and strong mobile support. With recent technological advances from Isomorphic Software and others, rich desktop and tuned mobile experiences can now be created with a single codebase – without compromising functionality, performance or usability. In his session at DevOps Su...
Dec. 1, 2015 02:45 PM EST Reads: 450
Dec. 1, 2015 02:30 PM EST Reads: 275
As organizations realize the scope of the Internet of Things, gaining key insights from Big Data, through the use of advanced analytics, becomes crucial. However, IoT also creates the need for petabyte scale storage of data from millions of devices. A new type of Storage is required which seamlessly integrates robust data analytics with massive scale. These storage systems will act as “smart systems” provide in-place analytics that speed discovery and enable businesses to quickly derive meaningf...
Dec. 1, 2015 02:15 PM EST Reads: 455
The annual holiday shopping season, which started on Thanksgiving weekend and runs through the end of December, is undoubtedly the most crucial time of the year for many eCommerce websites, with sales from this period having a dramatic effect on the year-end bottom line. Web performance – or, the overall speed and availability of a website or mobile site – is an issue year-round, but it takes on increased importance during the holidays. Ironically, it is at this time of year that networks and i...
Dec. 1, 2015 11:15 AM EST Reads: 176
Countless business models have spawned from the IaaS industry – resell Web hosting, blogs, public cloud, and on and on. With the overwhelming amount of tools available to us, it's sometimes easy to overlook that many of them are just new skins of resources we've had for a long time. In his general session at 17th Cloud Expo, Harold Hannon, Sr. Software Architect at SoftLayer, an IBM Company, broke down what we have to work with, discussed the benefits and pitfalls and how we can best use them ...
Dec. 1, 2015 10:45 AM EST Reads: 142
Discussions of cloud computing have evolved in recent years from a focus on specific types of cloud, to a world of hybrid cloud, and to a world dominated by the APIs that make today's multi-cloud environments and hybrid clouds possible. In this Power Panel at 17th Cloud Expo, moderated by Conference Chair Roger Strukhoff, panelists addressed the importance of customers being able to use the specific technologies they need, through environments and ecosystems that expose their APIs to make true ...
Dec. 1, 2015 10:00 AM EST Reads: 584
It's been a busy time for tech's ongoing infatuation with containers. Amazon just announced EC2 Container Registry to simply container management. The new Azure container service taps into Microsoft's partnership with Docker and Mesosphere. You know when there's a standard for containers on the table there's money on the table, too. Everyone is talking containers because they reduce a ton of development-related challenges and make it much easier to move across production and testing environm...
Dec. 1, 2015 10:00 AM EST Reads: 661