This past week was an exciting week. I had my first opportunity to attend the PMI Global Congress in North America. Thanks to PMI for covering the conference fees and selecting our presentation on engaging leadership for the healthcare track. I would definitely recommend making it to the local congress if you can. It is a wonderful networking and learning opportunity. Below are several conference highlights.
The Healthcare PMI Community of Practice has released a healthcare standard. It should be posted upon their website shortly. It went like hotcakes at the conference, so I'm hoping to get a copy soon.
The conference has your global sessions, and then areas of focus. Several others have commented upon the global sessions, I'm going to drill on down to the some of the education sessions I had an opportunity to attend. I did focus upon the Agile Track.
My favorite session of the congress was Natalie Nee's Agile: Still the Magic Bullet or Do you need a blended solution? The presentation depicted a well thought out approach of how to adopt agile. It was considerate of the environment needed to make agile successful and how to facilitate the adoption in a pragmatic manner within the organization. A key take a way was that agile does not need to be applied careless to every project. The methodology should be utilized when it makes sense for the project given the environment.
The other two agile sessions I attended were Taking off the Agile Training Wheels, Advanced Agile Project Management using Kanban by Robert Tarne and Large Scale Program and Portfolio Management with Scrum and Kanban by Mike Cottmeyer. Kanban refers to having a repeatable process and tracking user stories across that repeatable process to determine the sprint completion timeframe. Scrum refers to the process of having a daily standup meeting engaging the committed members to relay what they have accomplished yesterday, what is planned for accomplishment today, and what obstacles can get in their way while looking at the current product backlog for this sprint. Both presentations offered excellent insights into apply agile to small organizations. It is obvious that this methodology still continues to evolve as organizations begin to adopt and apply the practice.
Ginger Levin presented Mentoring: A Key Competency for Program and Project Professionals. She portrayed the criticality mentoring is for career success for the mentee and how to develop and implement a mentoring program. A key learning from this presentation is that mentoring programs should be a part of the enterprise PMO's repertoire and be managed as a project with a business case, clear success factors and desired business outcomes. - a great suggestion for developing yourself, others, and your workforce. Ginger Levin has several books on the market. She's a pretty smart and experienced lady so if you have a chance to buy and read her works, it is time well spent.
Another session I was fortunate enough to attend was Nayan Patel's a pragmatic journey to project portfolio metrics for a CIO. The presentation shared Baylor Health's PMO growth and development to the current practices. I'm glad to know we all suffer the similar growing pains as we first try to capture the project efforts in a dashboard to developing governance and determining which projects are priorities. The key also of resource forecasting and current utilization was quite thorough. Baylor has about 3900 beds and 650 IT Staff, so they have a large centralized IT department. Even in these tough economic times, the information provided from the pmo has enabled the growth of the department as the organization strives to achieve ICD10, meaningful use and several other endeavors.
All in all it was a good congress, Hopefully I'll be able to attend the next one.
Remember the cavalier way of implementing a solution back in the good old days. In some manner, a request was approved for a new system. Instead of looking out for a canned commercial solution, there would be a meeting a gathering of business requirements. There would be an in depth understanding of the existing paper business process and a way to automate it. Afterwards, there would be the construction, testing, deployment and fine tuning. Oh the chaos, and oh the understanding of how the hospital business worked.
Perhaps we need to consider what we have lost as we have moved to implementers of packaged applications. Rare is it now that a solution Is built from scratch. We all know the reasons, it is costly to construct and maintain. However, as we strive to implemented canned commercial applications for achieving meaningful use, icd10, or some other supply chain initiative. We have to consider what we have at risk and take some of those key solution development practices over to implementation of commercial packages.
As IT, we need to still utilize those practices of requirements gathering and weighing the must haves with the nice to haves. We should be vigorous in understanding the existing business process and what needs to change to adopt the new solution. Most of all we should convent and understand what gives our hospital the competitive advantage of other facility up the road. We should assure the solution will give the opportunity for that competitive advantage to have an agility as it matures.
After all, with the growth of software as a service and cloud computing, the one thing which should not be standardized is that which gives us our competitive edge.






