Brightmoon Consulting & Training

Your Agility Ticket - Scrum Workshop
Please refer to attached flyer (3 images) for greater details.

Who We Are
Allow us to briefly introduce ourselves - Brightmoon Consulting & Training. We have combined experience of 30 years in Software Development and Project Management. We are certified with two leading Scrum advocates - ScrumAlliance and Scrum.org. Our passion is to nurture the success of others in delivering successful software projects via Scrum.

In Need of Practical Knowledge in Scrum
Many companies are aware that they need to be highly agile to meet market dynamics. Thus, many of them introduce scrum/ agile into their work. However, many are unable to reap much benefits of scrum. Primary factor is they don't have practical knowledge and skills to make scrum work for them. Most of the existing trainings emphasizes on certification and not much on its practicality and usage. Therefore, it inspires us to share our passion in Scrum to you.

One of the most commonly used tool for strategic analysis is the SWOT. SWOT is acronym for Strengths, Weaknesses, Opportunities and Threats.

Strengths and Weaknesses represents what are within an
organization's direct control. SW analysis is basically inward looking and analysis. Some people call it internal analysis or soul searching. You ought to be really sincere and frank about strengths (don't over rate them) and weaknesses (don't under rate them). Admitting to have a weakness may not seem favourable to certain people or organization !!

Strengths are positive attributes for an organization. They are the internal factors that will contribute for the continuous survival or progress of the organization.  And it must not be something that everyone has as that does not give you any advantage.


To identify your strengths, ask yourself these kind of questions:-
i) What do I have that my competitors don't have ?
ii) Why are my customers coming back to me ?
iii) Why I am able to still gain profit ?
iv) Why do my products and/or services sell well ?

Weaknesses are negative attributes for an organization. They are internal factors that are detrimental for the organization or its business. To identify your weaknesses, ask yourself these kind of questions :-

i) Do my employees constantly complaining about a HR policy ?
ii) What do my competitors have that I don't have or hard to get or failed to retain ?
ii) Why is my competitor gaining higher market share every year ?
iii) Why are my staffs leaving the organization to join a competitor?

Opportunities and Threats are outward looking. Its external analysis. It
about analysing what are happening out there that concerns you directly and indirectly. Its about being sensitive to political, economical and
environmental changes that are happening and going to happen in the
immediate near future.

Opportunities are positive happenings. If it happens it is going to give positive impact to you or organization. You will usually capitalize on your strengths to benefit from the opportunity. An opportunity can also help to reduce the negative impact of your weakness.

Threats are something everybody wish they will not face. However reality is that it will be always there. Dealing with threats will increase your cost of doing business.. But you might vanish if you choose to ignore them. The point is to face and address them. But how would you do that if you don't know what are the threats that you are facing now and are sure to come ?

To identify your opportunities and threats, ask yourself these kind of questions  :-
i) Is there any new trade agreement going to be signed between Malaysia and Thailand ?
For example, a trade agreement between Malaysia and Thailand,  can be an opportunity or threat to an organization depending on where they are  in  the value chain and what are being discussed or agreed in the agreement. 
ii) General election is scheduled to happen early next year. How is it going to impact my business ?
iii) The KLIA airport is expected to be closed for 2-3 weeks in December due to forecasted very bad whether and typhoon. How is it going to impact my business ?

If you need help for someone to facilitate your discussion, do contact us.

Regular PMOs are tasked in setting project standards, monitor and control projects, and provide visibility to management team. Some PMOs are only serve as a administration service provider to projects, e.g.: status reporting.

Such activities above formed the foundation of a PMO and nothing flawed about it. When a PMO possess such visibility and influence over projects, its latent of become a strategist in an organization is often overlooked and undermined.

The basic tasks of a Strategist PMO are:-

1. Project Selection
When an organization is presented with many opportunities, it is equally vital to select right prospects/ projects that able bring an organization closer to its strategic goals. Shortlisted prospects will be evaluated to ensure its viability and feasibility.

For example, an organization wanted to introduce complete Project Management system, it needs to ensure the deliverable of its turnkey software development projects are able to become a complete Project Management system. Otherwise, the organization need to invest separately to materialize its goal.

2. Project Evaluation
Evaluation comprises of both technical viability and financial feasibility. The ultimate focus is on the financial feasibility of a project. Because the results of technical viability study will be translated to dollars and cents.

Among those financial evaluation methods are average rate of return, internal rate of return (IRR), net present value (NPV), and payback period. Cost of capital (cost involved in getting funding) is part of this evaluation.

3. Project Prioritization
Shortlisted prospects/ projects are prioritized with others prospects and existing projects. Every organization has limited capability to run certain number of projects. Thus, prioritization of projects is certainly unavoidable. In this exercise, some prospects/ projects have to be dropped or terminate prematurely.

When an existing project will be replaced, its salvaged value and adversarial impacts need to be seriously evaluated and handled. This premature closure entails severe impacts to its respective stakeholders, such as clients and project team. Thus, the success of replacement rely on the maturity of an organization and the effort of change management.

What's Next
In order to protect interest of an organization and remove favoritism, PMO has better position to objectively select, evaluate and prioritize the prospects/ projects. The existence of projects is heavily influenced by political landscape. Such Strategist PMO should reports directly to Board of Directors and not to single person. The PMO Head plays utmost critical role to ensure its objectivity.

Now you can take a step back to think how to nurture the strategist within your PMO.

1. Formulate or revise Business Case - outline authority and accountability of Strategist PMO
2. Solicit right candidate as PMO Head - ideally this person should possess strong knowledge of PMO and industry knowledge/ experience
3. Communicate the Business Case of Strategist PMO - prepare everyone to accept this newly arrived strategist
   
4. Regularly monitor performance  - this is ensure this strategist is properly nurtured with right support within organization

In this social computing and knowledge management era, companies are moving very fast. They have to. Otherwise, they will loose out to competition. But some companies are simply doing what others especially their competitors are doing like the road runner who will always end up getting hurt.

The question is, are you moving to the right direction ? How can you analyze it ? How can you validate it ? It is not so easy but it is not impossible either.

There are many tools that we can use to analyze whats coming, are we ready for them, if not what do we need to do,  are we moving to the right direction, are we doing the right things and many more questions at the strategic level.

In the next few weeks, we will write about what are those tools and and what kind of discussions you can have with your colleagues to help you develop your strategy and set your company direction.

When you sign-up this HRDF claimable training, Mysterious Gift (worth more than RM 50) is yours:-

1. Mention Brightmoon Consulting & Training during registration
2. Email a copy of your registration to info@brightmoon.com.my
   

This is our programme market under Comsystem Solutions, and hope to see you there.

Scrum framework focuses on producing incremental deliverables in short and regular intervals (e.g. 2 - 4 weeks). Thus, it is well received in many software development projects. Subsequently, other industries are adapting Scrum framework to combat uncertainties and remain responsive to deliver better customer satisfaction.

Now the question is - what is the possibility to implement a PMO by using Scrum?

Roles

• Product Owner (PO) - Appointed from business that responsible to prioritize deliverable, clarify requirements and ultimately accountable for the success of PMO implementation.
  
• PMO Team Members (Team) - SMEs (subject matter experts) or consultants that are tasked to develop and implement PMO services, processes and tools.
  

• Scrum Master (SM) - Recruited to the team as a facilitator to ensure Scrum framework is practiced correctly and consistently. For matured Scrum practicing organization, this role is optional.
  

Events/ Activities

• Sprint Planning - PO explains his/ her requirements based on Product Backlog; the Team clarify and estimate the duration needed. Upon agreement, each Team member get the tasks they can performe. Thus, the sprint starts.
  
• Daily Scrum - SM and the Team have daily meeting (15 minutes max) to discuss:-
  1. What has been done yesterday?
  2. What is planned for today?
  3. Any road block or challenges faced?
• Sprint Review - At the end of sprint, the deliverable is demonstrated to PO for acceptance.
  

• Sprint Retrospective - This is the time everyone evaluates the working processes and agreement (a.k.a. lesson learned):-
  1. What worked?
  2. What did not work?
  
• Backlog Grooming - PO sought second opinion from the Team to breakdown Product Backlog Item into smaller and manageable deliverable.

Artifacts

• Product Backlog - Owned by PO and it's a road map of PMO.
• Sprint Backlog - Owned by the Team and it's their work package of a sprint.

Critical Success Factors

• Product Owner has:-
  1. authority and accountability on PMO's direction.
  2. appreciation on the values and benefits of using Scrum.
  3. the trust on the Team's capabilities and competencies.
• Team has:-
  1. formed their own working agreement and adhere to it.
  2. mutual respect to each other despite they may have difference in opinions.
  3. accountability for their individual deliverables and performance.
  
• Scrum Master to:-
  1. educate both PO and Team to use Scrum framework consistently and effectively.
  2. protect the Team from anybody including PO on possible re-prioritization or addition of new features mid-ways.
  3. seek to resolve the challenges faced by the team.
• Ensure Entire Scrum framework is adopted and adhered to to gain intended benefits of it.
• Regular Inspection and Adaptation - When something is not working, everyone goes back to retrofit on how things are done (i.e. working processes and agreement) and not finger pointing on anyone.

Conclusion
As cited in The State of Scrum (June 2013), Scrum has gained its popularity and earned its successes outside of software industry. The approach to use Scrum to implement PMO is truely ground breaking and need a lot of courage to bring this to fruition. Thus, everyone in the team plays their role to make this a success.

May the Scrum Forces be with you.

Some may argue there is no such thing as pseudo-PMO or PMO-wannabe; PMO is a serious business and not for kids. While others may detest the needs of PMO in small organizations; literally they know everything like the back of their hand, and as they call everyone there by name.

Why Small Organizations
Nowadays, more and more small organizations are handling their business - the project way. They call their contract as "project." The person in charge is called "project manager." Each project is formed temporarily and tasked to deliver services/ products unique to each client. Meanwhile, project manager is responsible to deliver the project on time, on budget and within agreed scope.

Why Pseudo-PMO
Due to various reasons (e.g.: budget, competent personnel), full-fledged PMO is not affordable to small organizations. Without support of PMO, their projects (a.k.a. business contracts) are experiencing unnecessary pains. Often they are fire fighting in the projects, which is a form of wastage. Ultimately, reduce profitability. Thus, they need some form of PMO to ease their pain and increase bottom-line.

Without any form of PMO, small organizations are most likely to suffer in following areas:-

Have you ever experienced this? Too many choices presented will end up no decision being made. That's mainly because we are unsure what the implications are for each selection.

In deciding which type of PMO (Project Management Office) to be adapted can place us in similar indecisive situation.

Let's take a step back, and see the menu of PMO. Generally PMO has three types:-

1. Supportive - this PMO provides administrative and depository support to project personnel, such as filing, template design, training & etc. Its authority over projects is very low. When an organization is reducing cost, this type of PMO is the first one to slash. And, its job can easily taken by a project administrator.
2. Controlling - this PMO provides governance on the projects. It provides and enforces Project Management frameworks/ methodologies with relevant tools and processes. Its authority over projects is moderate as higher management can override its decision. When an organization is downsizing, it is the second to slash. Part of its jobs is transferred to higher management, and the rest is left on uncharted island.
3. Directive - this PMO has full authority over projects. At the same time, it has full accountability on the project performance. Only matured organizations will go for this. The primary benefit is the organization utilizes projects to gear the direction. Should any mismatched projects detected, they will slash the projects. And, keep the organization moving forward.

In order to successfully implement specific type of PMO, the organization's maturity plays a vital role. If your organization is unsure which type of PMO to adapt, try find the answers for the following questions:-