Thursday, 30 April 2015

Project Management fundamentals

Project Management Fundamentals

What is a Project?
A project is defined as a temporary endeavor or effort to create a unique product, services or results. 
  • The outcome of the project is not temporary. It has definite start data and end date.
  • A project is progressively elaborated. As more information is available the plans are elaborated.

What is Project Management?
The project management can be defined as applying knowledge, skills, tools to project activities to achieve project objectives.
Project activities includes works that will produce the deliverable, Estimating cost and estimating resources are the example of project activities.
Meeting scope, cost and time are the main objectives of a projects. However meeting customer satisfactions and customer expectations are the implicit project objectives.


 Project Constraints:
Project Management includes dealing with constraints that keep surfacing throughout the life cycle of a project. The most common set of constraints are cost, scope, time, quality, risks and resources.
Relationship among project, program and portfolio:

Portfolio: Portfolio is a collection of program put together to drive the strategic objectives. It may not be all related program.
Program : Program is a collection of related projects put together for better management. Example a program may have common resources which can be use effectively.
Project: A project is defined as a temporary endeavor or effort to create a unique product, services or results. A project may have sub-projects.

Operational Management: Operation management is a ongoing activities which has repetitive deliverable whereas the project management is a temporary endeavor which has unique deliverable.

Role of a Project Manager: Responsible for planning, executing, controlling and closing a project. A temporary role limited to project duration.


Enterprise Environmental Factors (EEF) - How company run the business?
Enterprise Environmental factors are conditions, situations or events in the company or in the market that directly or indirectly influences the project success.

Example of EEF: 
  • Market Place conditions
  • Company culture and structure
  • Risk tolerances
  • Project Management Information System (MIS) - how the company run the projects
  • Work Authorization System
  • Government regulations 


Project Life Cycle: Project life cycle is defined as collection of phases. Projects are divided into phases for better control and management. It focuses on managing the work that is required to produce the deliverable and accomplish the objective of the product. 
A life cycle determines what work need to be done in each phase, who is involve in each phase how to control and approve each phase.

Phase End Review: The phase is marked by the completion of the deliverable. The completion is marked by phase end review ( kill points, phase exits, phase gates) where "go ahead" or "no go ahead" or postponement decision is taken.

Notes:
  • Cost and staffing are low at the early phases, rise in the middle phases and fall in the last phases.
  • Risk of failing is high at the starting phase and risk of failing is low at the last phase.
  • Cost of making changes increases from the early phases to the later phases.
  • Ability of stakeholders to influence the project reduces from the early phases to later phase.
Product Life Cycle: Process of managing entire life cycle of a product from its conception, through design and manufacture to service and disposal.

Project Stakeholders: Project stakeholder are individuals or organization who are actively involved in the project and whose interest may be positively or negatively influenced by the project. 

Example of stakeholders:
  • Project Manager
  • Customer/User
  • Performing organization
  • Project Team Members
  • Project Management Team
  • Sponsor
  • Influencers
  • PMO
Integration Management: Integration Management is about coordinating or bringing together all the different processes and activities in a project.

Importance of project charter:

The project charter is a result of charting or formal initiating a project. It document that formally authorized a project or phase.

Project Authorization: Not having formal authorization for starting a projects can result in failure due to lack of support and misalignment. The process of authorizing a project is aim at preventing these common reason of project failure.

Lack of authorization process will cause effect:

  • Decline in profit
  • Project with no end date
  • Lot of rework
  • Duplication of work
  • Loss of opportunity 
  • Frustration  
Documenting initial requirements: The develop project charter process also focuses on documenting initial requirements. The stakeholder expectations and needs are converted into high level requirements as a part of developing project charter.

Linking customer and the project:  The develop project charter process also focuses on linking customer and the project. If the project is internal the linking is between the performing organization and the project.


Content of Project charter:

1. Project Purposes: Why the project is undertaken? Justification of project undertaken. Reason why we have taken the project -may be for ROI.

2. Measurable Project objectives - Mentioned all the objectives'
3. High Level Requirements - Get requirement from initial documents
4. High Level project Description:
5. High level product characteristics:
6. Summary milestone schedule
7. Summary Budget

Input to the project charter: 

Statement of Work (SOW)-SOW is a narrative description of product or services to be delivered.

The project statement of work contains following information.

  • Product Scope Description- Characteristics of the product. Deliverable at high level

For external project the SOW is provided by the customer sometime in the form of RFP, RFI and RFB.
For the internal project the SOW is provided by the sponsor.

Business Need - Give the justification and reasons of the project. Why it is initiated? What the project result will translate to business objectives.

Contracts-Commercials details. May not have detailed requirements.

EEF: Market Place conditions ( Demand and Supply, Currency Exchange fluctuation etc),  government regulations

 Organization process: - 
Company culture and structure
Project Management Information System (PMIS)
Work Authorization System
Risk tolerance- risk taker vs. risk averse

Develop project Management plan - It contains process ( how the project will be defined, executed, monitored, controlled and closed), management plan (subsidiary plans) and baselines( Scope, cost and schedule).
(Processes + subsidiary plans) + Baselines + other details==> Project Management Plan

Direct and Manage Project Execution: Performing or getting work done as per the project management plan.  Performing the work and creating deliverable are the 2 elements in this.


Approved changed request are authorized changes to the project. Only approved change request to be implemented and shall update the project plan. Approve change request include approved corrective actions, approved preventive actions and approved defect repair.
The change request remains as recommendations until they are approved. When they are approved by the CCB then it is called approved change request.

Monitor and control project work:  Monitoring refers to collecting, measuring, analyzing and distributing work performance information throughout the project life cycle. Controls refer to the action taken based on the work performance information. This sometimes results in change requests. Note that only approved change request shall be implemented. The rejected change request shall be documented.

Close project or Phase:

Close project includes formally closing project or Phase by finalizing all the activities across all the process groups.The final product, services or results needs to undergo formal acceptance and handover. The formal acceptance and handover is provided in the form of a formal statement confirming completion of the deliverable.


Scope Management:

The scope management is concern with defining the work to be done in the project. From then it is controlling the scope.
Process of scope management:

  • Defining the scope
  • Creating WBS
  • Obtaining formal acceptance of the deliverable
  • Controlling the Scope
Collect the requirements: Project charter and stakeholder registers are the main input to collect the requirements.

Below is some of the tools and techniques use to collect requirements.
 Interview- Interview are conducted to elicit the requirements with the key stakeholders. Sometime interview is done one to one basic. However it is a time consuming process.

Focus Groups: Discuss are been done with domain expert or SME. Some discussion are also conducted with other department to get their requirements and attitude towards the project.

Facilitated Workshop: Different workshop conducted with the key people and with the cross functional team.

Prototypes:  When the user requirement is not clear or when design is not clear or there are history of the communication problem , then we should go for simulation of the product to get the requirements.

Observations: End user can give input as to how it is performing or how it is working.

Questionnaire and Survey: Sometime offline question are shared and offline survey is done.


Group creativity technique: 
Brainstorming- It is used to generate a large number of ideas, risk, solution or gather lot of information for decision making , priority setting or planning. It should be free flow idea and no judgement is passed.

Nominal Group Technique: It is used to rank the most useful ideas, risks and solutions for further brainstorming.

Delphi Technique is used to reach a consensus of expert opinion anonymously. No bias and no grouping is allowed.








Sunday, 5 April 2015

Spectrum Auction 2015 - A step towards better India


    Spectrum auction 2015 and its role to shape up "Digital India" image. 

By Biplab Mallick 


On February 26, Honorable SC had allowed the centre government to go ahead with the spectrum auction which was scheduled from March 4 to March 25 2015 in all 22 service area and 19 circles. The historic spectrum auction of 800 MHz, 900 MHz, 1800 MHz and 2100 MHz is completed after 19 days and 115 rounds of bidding. The auction made the government richer by nearly Rs.1.1 lakh crore of which nearly Rs 29,000 crore will be received in over next 10 days of bidding. These upfront payments will help the government to meet its fiscal deficit target of 4.1 per cent of total GDP for 2014-15. This auction is termed as stupendous success as the government received nearly 67% more than expected revenue.  
But did this spectrum auction meet the intended objectives and will it act a stimulus to the growth of telecom industry, what role it will play to the government’s “Digital India” program. Before I analyze and answer these questions, I will touch upon on the auction objectives, how auction process is design to meet its objectives, who are the players and their role on influencing market demand and industry reaction to it.  
There are 8 bidders who are eligible for the bids. Uninor is the only operator who has not won spectrum in any telecom circle across all four bands. Capital investment for the other bidders  and their spectrum bandwidth holding are in the figure.


Below is the bandwidth purchased by Operators in various band:



The Aditya Birla group company Idea Cellular won 79.4 MHz spectrum and paid the maximum amount of Rs. 30252.88 crore. Mukesh Ambani’s Jio spend nearly 10K crore for 4G and bought 48.75 MHz in 800MHz band and 28 MHz in the 1800 MHz band. This spectrum auction was crucial for the top operators as they have to retain spectrum in service area for business continuity.

GOALS AND OBJECTIVES OF SPECTRUM PRICING:

For any resource including Radio Spectrum, the primary economic objective is to maximize the benefits to society such that there is efficient distribution of the resource resulting in maximum benefits to society.

Major spectrum pricing objectives of India as mentioned in the NTP’99
  •  .Spectrum be utilized efficiently, economically, rationally and optimally
  • Transparent process of allocation of frequency spectrum for use by the service and making it available to various users.
  •  To make adequate spectrum available.


Broad Goals of Spectrum Pricing include:

  • ·         Optimum utilization of Spectrum
  • ·         To promote competition and adoption of innovative Services
  • ·         To balance requirements of Commercial and non commercial users
  • ·         Public Interest
  • ·         Maximization of economic and social benefits
  • ·         To cover costs of spectrum management borne by the concerned Authority
  • ·         Revenue for the Government

VARIOUS APPROACHES OF SPECTRUM PRICING

  Spectrum is either valued using prices in market transactions (auctions, spectrum trading or leasing) or by administrative means. Simultaneous Multi-Round Ascending auctions and Combinatorial Clock Auction is of interest here.

Simultaneous multi-round ascending auctions (SMRA):

In this type of auction, all lots are simultaneously on offer over multiple rounds of bidding. Bidders may bid on any lot or combination of lots in each bidding round. At the end of each round high bids are disclosed and all bidders can bid again in the next round to become the high bidder. In general, after a round with no more bids, the bidders holding the high bids in the previous round win the lots. SMRA auctions were developed for use when there are spectrum lots that are complementary or substitute for the buyers’ business purpose, as they allow flexibility in bidding.

Combinatorial Clock Auction (CCA):

The Combinatorial clock auction (CCA) is a price clock-based auction format used to sell multiple lots for different categories in a single process. It provides bidders with the flexibility to bid on different combinations of lots. The CCA format also creates incentives for bidders to bid their full value for the lots.

The present auction is being conducted online and is termed as a Simultaneous Multiple Rounds Ascending (SMRA) e-auction.   

Bidders have a choice of paying the full amount upfront or defer it by paying 33 per cent of bid amount in 1,800 MHz and 25 per cent of bid amount in case of 900 MHz within 10 days of auction close. There is a moratorium of 2 years of payment of balance amount which shall be recovered in 10 equal annual instalments which will attract an interest of 10 per cent. There are two stages in the auction – Clock stage and Frequency Identification Stage. The clock stage will establish the bidders and number of blocks to be awarded in each service area while the second stage will identify specific frequency blocks for the winning bidders. Auctions on 800 MHz, 900 MHz, 1800 MHz and 2100 MHz the spectrum bands are being conducted simultaneously and online.


How significant this auction to the operator?


India's mobile connections will exceed 900 million to achieve 72 per cent penetration by 2016. Also, total mobile services revenue in India is projected to reach USD 30 billion in 2016. Also the telecom industry will have major role to shape up “Digital India” campaign initiated by the government of India.
While the winners get the exclusive right to use the spectrum, those who have lost the bid in that area will not be able to operate in it. They will not be able to get subscribers in the area where they do not have a licence. However, if a consumer has a connection of the particular telecom operator and travels to an area where the operator is not present, he will be charged interconnect user charges. 

Did the auction meet intended objectives?

The spectrum auction concluded after aggressive bidding which helped the government garner commitment of Rs 1,09,874 crore from operators. The government were able to generate more revenue than expected. The bidding was very competitive and an equal level playing field was created for all the operators. However more capital was extracted from operator. Most of the operator is already debt-ridden and this additional financial burden will alter the financials and cost structure of the operator. The operator will have uphill task of more investment to rollout all the services and application as committed to government. Consequently for the existing player tariff may increase to meet the commitment of government. For the new entrant the only way to increase the subscriber base as early as possible after rolling out innovating services and application.

Future of Indian Telecom industry:

After this auction most of the operator is upbeat to provide next level of services in the telecom industry. The introduction of 2100MHz spectrum for 2015’s auction has created a new growth market for LTE market for the first time. 
Bharti Airtel will be able to offer pan India 4G services using a combination of FD-LTE technology in the 1800 MHz band and TD-LTE roll out in the 2300 MHz band. It will also be able to offer 3G across all markets with the exception of Kerala using a combination of 900 MHz and 2100 MHz. The company was also able to renew its entire spectrum holding which ensure the continuity of business.
Vodafone India plans to expand its 3G service over its own network from 9 circles to 16 circles after ensuring continuity of their existing business.
 Idea Cellular plan to expand its 3G Services to 13 circles covering 80% of its overall revenue and enable 4G roll out on 1800 MHz in 10 Service Areas.
Reliance Communication will transition existing 2G customers in the remaining 3 circles to 3G before December 2015.
Jio plans to provide 4G services using LTE in 800MHz, 1800MHz and 2300MHz bands through an integrated ecosystem.
Finally delivering the “Digital India” will require a more collaborative approach between the mobile operators themselves as well as through collaboration with governments, regulators and other industry stakeholders.

Thursday, 2 April 2015

       Risk Management in System Engineering
                                                       By Biplab Mallick

I have spent more than decade in telecom software product development and deployment in the service provider network.  System Engineering is a lifecycle disciple and the nature of this disciple depends on the nature of the project and system.  On typical technical product development projects, the systems engineering efforts are responsible for managing, directing, executing, controlling and supporting an array of technical disciplines.

Systems engineers are closely related to the discipline of project management. In some cases, project managers will need input from systems engineers to organize things like scope, cost and Schedule estimates. In some cases, systems engineers will need assistance from project managers in order to do their job. There is a very strong correlation between the systems engineering effort and the project management effort.

Here I will look at some key systems engineering management challenges arise and try to explain why they are important.

1.    Verification and Validation- The manager has to ensure that system engineering process are delivered its expected results and fit for the uses and customer is really satisfied with the final product. It is required to device comprehensive test program for the above verification and validation.  The comprehensive test program will have different test strategy, testing methodologies likes deliverable testing, feature testing, system testing, performance testing and acceptance testing depending on the nature of the system. The challenges here are that most of the time the schedule, budget and risks will not be known in advance. Unless these are managed properly system will be useless and complete testing plan will be failed. The bottom line is that verification and validation of the system is a critical part of systems engineering and it must be planned and managed from the earliest possible stage in the systems engineering lifecycle.

2.    Configuration management (CM) is a very important part of systems engineering. It is there to make sure that we maintain control over the versions of all of the different components within our system design. This includes our documentation (such as software requirement specifications and design) and the hardware, software and interfaces that make up the design. A typical Configuration management (CM)  will involve following elements :
•         Firstly, identify everything that we are going to place under control. It might be that the version of software running on some of these computer-based systems.

•     Once the components are identified what we are controlling, communicate that to all stakeholders.

•         The other critical element of configuration management is the ability to be able to manage change. Change is not bad in itself but change without adequate control and visibility is potentially disastrous. Change management is all about being able to gather the appropriate stakeholder together and look at change proposals. The cost and schedule impact of the change could be discussed and a decision can be made about whether to make the change or not.

•         Finally, configuration management also involves periodically auditing the process to make sure it is all working properly. We check that everyone is using the latest agreed documentation in performing their work and we confirm that the materials being used and the construction process being used is in accordance with the design documentation.

Managing the configuration of all of the components of system can be tedious but if it is not done properly, we will fail to support stakeholders as we attempt to support a system whose configuration is not known. Imagine trying to deploy multiple systems ( e.g Femtocells) in telecom service provider’s networks where there seems to be significant variation in configuration across the systems that are meant to be identical.

3.    Technical Risk: System engineering is a disciple where a lot of technical risk will surface in time to time.
Technical risk could include delivering a system that:
• is not up to the required standard in terms of its function and performance,
• is not able to be maintained in accordance with the support concept,
•is not sufficiently reliable to carry out its intended mission. e.g increasing the load to the system does not deteriorate the performance of the system.
•is too expensive or difficult to produce in the required quantities.

Systems engineering is a discipline that continually assists with risk management. For example:
•         conduct progressive design reviews as we pass through the design phase to try to detect and correct      errors as early as possible,
•         Conduct critical review programs and audits as the system passes through design to development and into construction and production to ensure that have come up with a properly documented design that works.
•         Other example of risk management to introduce redundancy in system.
•         When a common mode of failure happen in system engineers may solve this by using the concept of design diversity where the load are transferred to the other system.



4.    Periodic review of in system engineering program:

It is very vital to do the review periodically at logical points in the design and development process. This is an effective way of detecting errors, conflicts or problems with the design as early as possible. After all, the earlier we detect issues, the easier and cheaper they are to rectify.

5.   Which development approach -Waterfall Model?

A fundamental systems engineering management task is to determine the most appropriate technical strategy to use to take our stakeholders’ expectations and turn them into a system that solves the stakeholders’ problems.
The development approach I am going to describe here is often called the waterfall approach because the whole system is developed in one pass.
•         It relies on a thorough and complete understanding of the problem and the desired solution.
•         It assumes the accurate translation of this into comprehensive system level requirements.
•         It works best when these requirements do not change very often
•         It assumes that technology is available and works best when that technology remains relatively stable over the course of the system development.
•         Technical expertise is sufficiently available and able to solve the problem at once
•         It assumes that enough time and enough money is available to solve the entire problem in one pass.
If any of those assumptions are not in place, then systems engineers should think of alternative ways of executing the systems engineering process. As an alternative to waterfall model, the industry is adapting new approaches like agile and incremental approach.  Forcing a waterfall approach under unsatisfactory circumstances will expose the program to risks such as cost and time overruns.


6.    Planning process- So far I have mentioned about what shall be done in system engineering process. Now we need to really have a plan and those plan are tracked to get the final results. In systems engineering, this plan is generally called the Systems Engineering Plan.
•         The plan should answer the followings:
•         What strategy are we using?
•         Who is doing what?
•         When are the reviews happening?
•         What design, development and production resources are required?
•         What are some of the big risks we are facing and what is the mitigation plan?
The plan will be always dynamic and need to update periodically to meet the challenges of changing situation.