Monday, October 22, 2012

How to Root Samsung Galaxy S2 Running on Android 4.0.3 ICS XWLPD Firmware

This method of rooting gives root access includes the installation of CWM recovery and the full access to run custom ROMs and special apps
Let’s head to the procedure to root Samsung Galaxy S2 I9100 running on Android 4.0.3 ICS XWLPD.

Download below required files first
Prepare your phone (satisfy the below pre-requisites)
  • Back up your Android phone.
  • Disable all security suites and firewalls including KIES
  • Must enable the USB debugging mode by following- Settings>> Applications>> Developments>> USB debugging. And here just ticked the “USB debugging” option.
  • Ensure your Samsung Galaxy S2 is at least 70% charged.
Procedure to root Samsung galaxy S2 running on XWLPD

Step 1. First of all you have to extract the downloaded file of CF- root kernel in your PC, and get the below file-
“CF-Root-SGS2_XX_NEE_LPD-v5.4-CWM5.tar”

Step 2. Launch the downloaded Odin3 in your PC and keep it opened. Make sure in Odin’s left side under the options Auto Reboot and F.Reset Time are checked.

Step 3. Switch off your Galaxy S2. Reboot your Galaxy S2 in download mode by- press and hold “Volume down” + “Home” + “Power” simultaneously until a warning message is displayed.

Step 4. Connect your Galaxy S2 to your PC using USB cable and wait for Odin to display the message in ID:COM section. It turns yellow and in message boxes “ADDED” appears, that means your phone is successfully connected and ready for update.

Step 5. Now click on PDA tab in Odin, and select the file you got after extracting zip file.
"CF-Root-SGS2_XX_NEE_LPD-v5.4-CWM5.tar"

Step 6. Click on “START” Button, during this process do not disconnect the cable or turn off device. Your phone will reboot when flashing is done.

Wednesday, October 10, 2012

Risk Management

Risk Management

Risk is encountered throughout the life cycle of a project. Some projects have more risks than others. A risk event can slightly or severely impact a project's success. Risk management is actually broader than managing potentially adverse events. Risk management includes both threats and opportunities. By definition, projects have risk. A risk management plan helps a project team manage that risk. 

The risk management plan (RMP) should be developed early in the life of the project. The plan should be revised when a risk event occurs, and on a periodic basis. Risks will change over the duration of the project. The frequency of periodic updates is dictated by several factors: complexity of the project, strategic importance of the project, and volatility of factors that could affect the project. Risk levels increase and decrease during the life cycle of a project, but a risk event can occur any time. It is important to distinguish between risk and a risk event. Risk represents a threat level to a project, while a risk event is the actual occurrence of the negative incident. A project that has an RMP can respond properly and more quickly to address an identified risk. 

A Risk Management Plan typically includes:
  1. Risk Management Planning (RMP) - Every project must address risk, but smaller projects can typically use a "canned" plan. All projects need to address risk. However, it isn't cost effective for every small project to build it’s own RMP. For that reason, organizations build a scalable template so that all of their project teams can use an RMP.
  2. Risk Identification – Ask your team early in the project to brainstorm about potential risks to the project.
  3. Qualitative & Quantitative Risk Analysis - determine the potential impact of each risk on the project.
  4. Risk Response Planning
    • Put the risk events in order.
    • Select the events you want to address.
    • Build a Risk Response Plan for the risk events you choose.
  5. Risk Monitoring and Control - done after the Risk Response Plan is defined. This typically includes the following strategies: avoidance, transference, mitigation, and acceptance (contingency plan). The risk changes as the project continues. Risk levels in some project areas increase, while others decrease. Risk is present during the entire life cycle of the project.
Communication Management

Managing communication is crucial to the success of any group of people. Communication plans are effective for many different groups, including project teams, management groups, and civic groups. You can build a communication plan in four easy steps. Typically, the project manager, project sponsor and key members from the project team meet together to build the communication plan. If you are building a communication plan for your management group, build it in a team meeting.

Steps to Building a Communication Plan:
  • Identify your key stakeholders.
  • Ask the key stakeholders what type of information they want to receive and in what format.
  • Document the communication strategies.
  • Obtain sign off from the key stakeholders.
Communication can take many forms. Written, oral, listening, and speaking are typical means of communication. It is important that communication approaches be made up of a two-way approach. 

Some examples are: speaking and listening, writing and reading, and sending and receiving messages. Finally, there are informal and formal communication forms of communication.
It is very important for project managers to be effective communicators. Clear, concise, and timely communication can add clarity to a complex project. A project manager must be able to effectively communicate across geographic, technical, and business boundaries.

Types of Meetings

Meetings are a common forum for communication.
It is important to note that there may be different types of meetings that take place throughout a given project. Some examples of meetings may include:
  • Project kick-off meeting.
  • Status review meetings.
  • Problem-solving meetings.
  • Design review meetings.
  • Post project evaluation meeting.
The Project kick-off and Post project evaluation meetings would occur at the beginning and end of the project, respectively. The status review, problem-solving, and design review meetings may occur throughout the duration of the project.