Excellentia 106
Excellentia 106
Excellentia 106
Build Resilience
in Any Kind of Project
I
like to think about resilience as a way Sometimes, your customers don’t 1. Create Deliverable-Based Plans
of using past performance and data want agile projects—especially If you’re using a phase-gate
to inform our next steps. if they are (or think they are) too approach to your projects, you’re
Agile approaches tend to build busy to offer you feedback. I would probably supposed to have gates
resilience into the work because of argue that those kinds of projects that end in “freeze” or “complete,”
the frequent build-release loop. The desperately need an agile approach. such as:
team builds something useful for the I might be correct, and that doesn’t
customer and then releases it. It then matter. If you can’t get the feedback,
builds the next thing and releases you might not want to try to create
or use an agile approach.
that. The faster the team can finish IN THIS ISSUE
work and release, the faster it can However, you might well want to
get feedback about what it built. create a project where you can take The First “Project Manager
What if you can’t use an agile the relative past and use data and Roast!”— Onsite Series
approach for some reason? You information to inform the next bit of Held in Chengdu................................. 4
might not have a project that lends work. In that case, I recommend you
PMI Indonesia Chapter Joins
itself to an agile approach because consider these three ideas:
Chapter XChange Initiative.... 5
your product contains hardware 1. deliverable-based planning PRANKS 20:
that’s not easy to upgrade. The cost 2. frequent internal releases Bluebird Strategic Trans-
of frequent releases dwarfs any formation Journey........................... 6
profit you make from the product. 3. frequent kaizens or retrospectives
PRANKS 21:
(Note: Most of my experience is in
software projects or events, so if your All Buttons Pushed! Dealing
projects differ from those, consider the with Conflict and Resistance -
ideas here and see if they’re useful to in times of the pandemic, and
you.) beyond........................................................ 7
The Annual Board Workshop
... continued on page 3 2021............................................................... 10
Part of the problem is what you call those milestones. Before I knew about agile approaches, I often used
When we name a milestone “freeze” or “complete,” we talk frequent internal releases. I’ve used them in several ways:
about outputs. Unless you say something like, “All design for 1. Create “phases” of releases: Release .1, .2, .3 and so
all requirements we know about complete,” you don’t have on. Because I named them as point releases (all building
an accurate milestone. up to the whole-numbered release), other people
And notice that business of “all.” I can’t remember realized the project was still in progress.
a project I’ve been on where we knew all of the 2. If you use deliverables, you can create interim
requirements until we shipped the product to the internal releases. You might even say, “This release
customers. Every project I’ve been on has had changes— only has search by geography, not by product.” That
even at the last minute. way, people realize what’s not in the release.
3. Release what’s done every month. Many years ago,
Outputs don’t specify enough information for us to use I used monthly release trains. We still created product
them to show our progress in a project. requirements documents, and worked according
Instead of outputs, we can define deliverables. Here’s an to the documented requirements. However, as a
example of deliverable-based milestones: company, we decided we would release whatever was
“Login screens design complete, code frozen, and ready internally so other people could use our interim
tested.” working product. This also works well with deliverable-
based planning.
That way, you and everyone else can see how the work
builds on itself. The more often you release deliverables, the more I
suggest you reflect—or use a kaizen, a form of continuous
Your organization might still want you to create a work improvement.
breakdown structure to separate each piece, as in:
3. Reflect Often
• Login screens designed and verified with user
• Login screens coded You might be familiar with larger retrospectives. However,
• Login screen tested after coding what if your team used a little kaizen on a weekly cadence
to learn what’s working and not working for the team?
When you create deliverables like these, you help other
people understand what “freeze” or “complete” might I recommend a 30- to 60-minute meeting weekly or
mean. In addition, the team can see the work they need to biweekly to resolve any specific issues that arose from the
do. team’s work since the last kaizen. The team sets aside this
small chunk of time to create action plans based on any
If your managers are accustomed to seeing progress issues that arose since the last kaizen. If you have time to
charts with just the top-level phases defined (analysis, do a more complete retrospective, that’s terrific. If the
design, code, test, release), they might not want to see all team doesn’t have more time, consider this as a minimum
the various feature sets separated. However, when you reflection tool.
use deliverable-based planning, you can create a much
more accurate schedule. Build Resilience Into Your Project
One of the ways you can tell if you’ve got the right I tend to use agile approaches for maximum resilience.
deliverables is to deliver inside the project as frequently as You don’t need to use an agile approach for resilience.
possible. Instead, consider deliverable-based plans, frequent interim
releases and frequent reflection to adjust the team’s work
2. Release Internally as Often as Reasonable and replan for maximum benefit to everyone.
Early in my career, I developed software for an analytical
chemical instrument. One of my roles was to “port” our
FFT (fast Fourier transform) to new hardware. That meant Johanna Rothman (Mass Bay
I needed to rewrite the code. Chapter)
Johanna Rothman works with companies
I as nervous about my code. We didn’t have a simulator to improve how they manage their product
that would run hundreds or thousands of tests. We also development. She is the author of Manage Your
didn’t have dedicated testers. However, the chemists and Project Portfolio: Increase Your Capacity and
Finish More Projects, 2nd edition, Agile and Lean
the other software developers had many scenarios. I said, Program Management: Scaling Collaboration
“If I deliver new code every day, would you run some of Across the Organization as well as several
your scenarios against my code?” other books including the newest: Create Your
Successful Agile Project: Collaborate, Measure,
My colleagues agreed to do so. Estimate, Deliver. See her blogs and more of her
writing at jrothman.com.
I delivered my changed code every day or two, and they
Group discussions
From
MEMBER
My Journey to pursue PMP certification started when I mentor also encouraged me to put
worked overseas. It was 2017. I had a discussion with some a date soon after my confidence
local PMPs about PMP certification. However, after some level reached the expected stage.
weeks of preparation, PMI announced that PMBOK 5th I measured my confidence level
edition will be updated and I decided to postpone my using some Exam Simulators. I put a
study. I restarted again to study PMP with PMBOK 6th date, and took the exam and finally
edition in mid 2018 with help and support from my Project passed the exam.
Manager here in Indonesia. At that time, it was not too
I would like to convey my
intensive a study since I was caught in the middle project
appreciation and thanks to all
with a tight schedule. March 2019, I encourage myself to
Mentors who have shared the
take the exam. I must pass the exam.
knowledge, motivated me and gave
Around August 2019, I got an email about a Study Group tips & tricks to Pass the PMP Exam.
program from PMI Indonesia Chapter. Sure I was excited I strongly recommend all PMP aspirants to attend Study
and must attend the Study Group. The Study Group is Group held by PMI, Indonesian Chapter. Again Thank you
quite tough. Every week before the Study Group, I must PMI, Indonesian Chapter.
submit 15 braindumps, answers of FAQ, and pretest,
ensuring that I am ready for the Study Group. The Study
Group is very useful, mentors are helpful and support us Reza Hanafi, PMP
with their knowledge. Study Group has helped me to raise Mentee at PMI Indonesia Study Group#16
my level of understanding of PMBOK more than ever. My Telecommunication BSS Professional
PRANKS 20:
Bluebird Strategic Transformation
Journey
In January 12th, PMI Indonesia Chapter held its first
Project Management Knowledge Sharing (PRANKS) in
2021 with Paul Soegianto, the Chief Strategy Officer
of Blue Bird, as the honourable speaker.
Soegianto has an interesting professional background
prior to his current position in Blue Bird as Chief
Strategy and some of his notable past positions were
Chief Operating Officer of Smartfren, part of RTS
Team of McKinsey & Company, as well as Operation
Manager of Airbus. Soegianto holds Master of Global
Management (honorary graduate) from Northern
Institute of Technology, Master of Science for Process
Engineering and Material Science from Technische
Universität Hamburg, in addition to his Bachelor of
Science degree from Universitas of Indonesia.
Soegianto shared the journey of Blue Bird strategic
transformation which started from when Industry
4.0 digital shift affected the transportation industry
that brings business and technical challenges. Based
on the company’s defined 4 transformation pillars –
People, Digital, Business, and Partnership – strategic
transformation for both business practices and
operational is swiftly executed when it is triggered
by the digitalisation and modernisation of point of
contacts between Blue Bird and its customers.
Another strategic transformation, Bird Kirim Logistics
– which is Blue Bird's new business unit for the logistical
distribution market, also occurred in 2020 in response
to the COVID-19 global pandemic.
This PRANKS session was successfully attended by 106
members & non-members. They joined wirelessly from
various places of Indonesia and beyond. If you want to
join, please stay tuned and register to the event. They
are conducted monthly and are published through the
Chapter’s communication channels.
CERTIFICATIONS
TOTAL
Total Active Holders
MEMBERS
627,346
CAPM PfMP
46,357 896
Certified Portfolio
PMI Fact File
Associate Management
in Project Professional
Management
PMP PgMP
Statistics through 31 September 2020
1,038,797 3,002
Project Program
Management Management
Professional Professional
214 countries and
territories
PMI has 306 chartered
and 7 potential chapters
50
40
30
20
10
0
New Member Renewed Member
January-20 45 52
February-20 15 29
March-20 14 41
April-20 7 37
May-20 14 25
June-20 16 20
July-20 13 24
August-20 11 37
September-20 20 30
October-20 37 36
November-20 34 42
December-20 44 36
January-21 20 38
52
45
44
42
41
38
37 37 37
36 36
34
30
29
25
24
20 20 20
16
15
14 14
13
11