September 22, 2008
The Rising Need of Project
August 11, 2008
What is Agile Project Methodology?
What is this agile project management and how does it matters in IT industry? In this blog, I am going to throw some light on Agile Project Management. This blog is s about Agile Project Management, which is a set of simple practices, which can easily be understood by development teams and enable them to concentrate on the most important aspect of the project, "delivery of the product to the users".
Today, every big and small organization relies on software, to be competitive and be successful. Well, it’s good news for technology / software professionals, but one should also note that today customers want the projects to be delivered as promised, on time and meeting or exceeding the quality expectations. In order to deliver any project well, as a project manager, you need to have a methodology or a process in place. According to Merriam Webster, a methodology is a body of methods, rules, and postulates employed by a discipline: a particular procedure or set of procedures.
Many organizations have been employing traditional development methodologies like Waterfall, Capability Maturity Model and others. However, in most of the cases it has been found these methodologies have not been able to deliver results in a typical short-cycle project. This is because, in most of the cases either they were predictive or they impose a disciplined & repeatable process, to increase predictability.
So, what type of methodology would help you and your team to deliver the product and satisfy the customers?
The methodology should be simple. The chosen methodology must be simple enough to enable the smart people to concentrate on business and technology and deliver products at a high speed. A methodology should be as simple as possible to get the job done. . One methodology that meets all these features is Agile Methodology. This methodology has helped many leading and mid-sized companies deliver results in complex project areas.
Agile places a lot of emphasis on teamwork. Customers & developers are on the same team. So, customers are always available to the developers for feature prioritization or product feedback. Simplicity is another essential component of Agile project. Simplicity provides a real value in high change situations. The team employs simple approaches in design and coding. It is very much people-oriented and empowers the developers. It is very suitable for a typical current day short-cycle project.
August 8, 2008
Why Projects Fails?
In this world every project is planned and meant to get completed right on time and within the predefined budget. But reality presents a totally different story. It's not uncommon for projects to fail. Today, even if budget and schedules are met, one must ask "did the project deliver the results and quality we expected?” True project success must be evaluated on three components i.e. time, quality and cost, otherwise a project could be considered a failure.
When projects begin to demonstrate signs of failure, everyone looks to the project manager for answers. It may seem inequitable that the burden of doom falls upon a single individual, but being a project manager, he or she must be able to recognize and deal with these types of situations. It is essential for project managers to have a better perceptive of the enterprise's business objectives so that they can continually measure their projects in terms of delivering these business objectives.
These days, business requirements change frequently and so it has become vital for project manager to be fully aware of the issues at a business level. Even a project that delivers the planned scope within time and cost may be deemed unsuccessful because its deliverables are no longer relevant to the business. the question is why project fails? Have you ever wondered why some projects go smoothly and others seem plagued with problems?
There are many reasons why projects (both simple and complex) fail; the number of reasons can be infinite. Some projects do not meet the strategic vision of the company. If business needs are not clearly defined, it will result in a project that does not add value to the bottom line or enhance business processes. Apart from this, some projects also fail due to in-complete project scope and unclear definition of the project's benefits. Moreover, inadequate funding, and incorrect budgeting is still a main cause for projects not delivering their objectives within the quality framework.
In addition to this, the lack of enforcement of policy and procedures also cause a project failure. Even though a policy has been established, it is not enforced. As a result, inconsistent results emerge. If a standard and consistent approach to project management is devised by a company, it must be routinely policed in order to assure accuracy and uniform results. It is one thing to enact legislation, quite another to enforce it.
Even with the best of intentions or solid plans, project can go awry if they are not managed properly. Thus it's the project manager's responsibility to correct the listing no one else. During the course of managing a project, the project manager must monitor activities (and distractions) from many sources and directions.
July 22, 2008
Project Management in IT Industry
Managing an IT project is not an easy job and today it is just like a juggling chunk of Jell-O. Information technology is especially slippery because it's always moving, changing, adapting and challenging business. Generally all projects are constrained by three factors: time, cost and scope and for any project to be successful, these three constraints must be in symmetry. If any constraint is out of equilibrium, the project increases its chances to head for disaster. In case of IT industry, all projects move through five phases in the project management lifecycle, i.e. initiating, planning, executing, monitoring and controlling, and closing. Each phase contains processes that move the project from idea to implementation.
However, in most of the cases IT projects frequently fail. According to the Standish Group, which tracks IT project success rates, only 29 percent of IT projects conducted in 2004 were completed successfully. The numbers are discouraging for a various reasons. A surprising statistic reveals the majority of IT projects, despite being planned, still end up not meeting outlined project goals throughout their planned course, both in terms of keeping with time and budgeting available money.
IT projects fail because due to a lack of sufficient planning. An IT organization must think the resources it needs to devote to a project, the skills required, the people who need to be involved, and practically judge the time it will take to implement the project deliverables. Nevertheless, with modern-day emphasis being on getting more bangs for the cash, IT has to manage projects more effectively. The constant growing challenge has led many IT firms from all across the world to turn to Project Management as a way to boost IT efficiency, cut costs, and improve on project delivery in terms of time and budget. Looking at the present picture of global IT industry, the ratio of IT projects has increased dramatically. In addition to this, with the constant increase of IT projects the call for IT Project Managers have also boomed. The IT project manager is the person who is responsible for the management of all activity necessary for the delivery of IT project so that it meets the expectations and satisfaction of the customer, within an agreed time frame and within budget constraints.
Though information technology training for IT project managers can help them upgrade their technical knowledge, but may not know how company’s technology fits into the bigger picture from a business perspective. The success of a project often rests on the understanding of related people and management issues, rather than technical issues. That’s where project management training becomes important.
Project management training addressing different areas of IT project management i.e. software, systems integration, communications and human resources can help project managers gain the experience, techniques and tools to manage each stage of project. By extending project management concepts into the IT arena, the IT professionals can gain an understanding of the strategies essential to handle IT projects of any size.
June 25, 2008
Risk Management Process - A Practical and Effective Approach
It is said that a strong risk management process can decrease problems on a project by as much as 80 or 90 percent. In combination with solid project management practices having a well-defined scope, incorporating input from the appropriate stakeholders, following a good change management process, and keeping open the lines of communication a good risk management process is critical in cutting down on surprises, or unexpected project risks. Today, one cannot deny from the fact that such risk management process can help in problem resolution.
However, there are certain steps whose absence can affect project risk management process. Here are seven-step risk management processes that can be effectively utilized to accomplish desired project result.
Step 1: Each person involved in the planning process individually list at least ten potential risk items. Often with this step, team members will assume that certain project risks are already known, and therefore do not need to be listed. For example, scope creep is a typical problem on most projects. Yet it still must be listed because even with the best practice management processes in place, it could still occur and cause problems on a project over time. Therefore it should be addressed rather than ignored.
Step 2: Collect the lists of project risks and compile them into a single list with the duplicates removed.
Step 3: Assess the probability, the consequence and the detect-ability of each item on the master list. This can be done by assigning each item on the list a numerical rating such as on a scale from 1 to 4 or a subjective term such as high, medium, or low. Detect-ability is optional, but it can be simple to assess if a risk is harder to see, such as with scope creep, then it's a riskier item. If it's easier to catch early, such as loss of management support or loss of a key resource, then it's lower risk.
Step 4: Break the planning team into subgroups and to give a portion of the master list to each subgroup. Each subgroup can then identify the triggers warning signs for its assigned list of project risks.
Step 5: Subgroups must be able to identify possible preventive actions for the threats and enhancement actions for the opportunities.
Step 6: At this stage the subgroups must create a contingency plan that should includes the actions one would take if a trigger or a risk were to occur. This plan has to be created for those risks scoring above a certain cut-off point, which are determined after looking at the total scores for all risks.
Step 7: Determine the owner of each risk on the list. The owner is the person who is responsible for watching out for triggers and then for responding appropriately if the triggers do in fact occur by implementing the pre-approved and now established contingency plan. Often, the owner of the risk is the project manager, but it is always in the best interest of the project for all team members to watch for triggers while working on the project.
Often, the steps in which triggers and preventive actions are identified are overlooked. However, these are vital to the entire risk management process. After a team has completed this exercise once, the members will be better conditioned on what to pay attention to while managing the project so they are more proactive in catching changes or issues early. If these steps in the risk management process are skipped, the team can find themselves in constant reaction mode, simply implementing a contingency plan for each risk after that risk catches them by surprise.
A risk management process does not have to be complicated or time consuming to be effective. By following a simple, tested, and proven approach that involves seven steps taken at the beginning of each project the project team can prepare itself for whatever may occur.