Skip to main content

Posts

Closing a Project using PRINCE2 Method - World Of Agile

The purpose of the Closing a Project process is to provide a fixed point at which acceptance for the  project product is confirmed, and to recognize that objectives set out in the original Project Initiation  Documentation have been achieved (or approved changes to the objectives have been achieved), or  that the project has nothing more to contribute. Main Objective of closing a project process are as follows: ·           To Verify user acceptance of the project’s products ·           To Ensure that the host site is able to support the products when the project is disbanded ·           To Review the performance of the project against its baselines ·           To Assess any benefits that have already been realized, update the forecast of the remaining ·           benefits, and plan for a review of those unrealized benefits post project. ·           To Ensure that provision has been made to address all open issues and risks, with follow-on action Recommendations for the Team Activities
Read more
Recent posts

The Service Value System - Continual improvement | ITIL V4 Certification

Continual Improvement Continual improvement takes place in all areas of the organization and at all levels, from strategic to operational. When provisioning a service we should always keep continual improvement in mind, and should always be looking for opportunities to improve. To support continual improvement at all levels, the ITIL® SVS includes: ITIL® Continual Improvement Model provides organizations with a structured approach to implementing improvements Improve Service Value Chain Activity Continual Improvement Practice Continual Improvement Model Continual Improvement Model can be used as a high-level guide to support improvement initiatives.  The model supports an iterative approach to improvement, dividing work into manageable pieces with separate goals that can be achieved incrementally. The scope and details of each step of the model will vary significantly based on the subject and the type of improvement The steps of this model do not need to be carried out in a linear fash
Read more

PRINCE2's Project Organisation

PRINCE2's organisation theme defines the Project Team or organisation. It establishes the project's structure of accountability and responsibilities. As PRINCE2 is based on a customer/supplier environment, it assumes that there will be a customer who will specify the desired result and probably pay for the project, and a supplier who will provide the resources and skills to deliver that result. A successful project management team should have business, user and supplier stakeholder representation. Business The products of the project should meet a business need which will justify the investment in the project. Should also provide value for money. The Executive looks after business interests User The user viewpoint should represent those individuals or groups for whom some or all of the following will apply: They will use the outputs of the project to realize the benefits after the project is complete They will operate, maintain or support the project’s outputs The outputs of t
Read more

Agile Administration in Tooling and Tool Integration

Tools are inherent to our jobs, inherent to how we solve the problems we face each day. Our comfort level with the set of tools that are available to us, and our ability to adapt to new tools as they evolve and shape our thoughts and ideas. The availability of collective knowledge within the palm of your hand combined with the collaboration across organization and company boundaries through open source software is dramatically disrupting the status quo of work. Companies mired in managing infrastructure configuration management by hand with unknown numbers of divergent systems, unable to quickly change and respond to market demands will struggle against their counterparts who have managed to contain their complexity on one axis through infrastructure automation. While it is possible to manage servers by hand, or even artisinally crafted shell scripts, a proper configuration management tool is invaluable especially as your environment and team changes. Even the best software developers
Read more

What is ITIL?

The term ITIL means "Information Technology Infrastructure Library". ITIL is the most popular and widely accepted approach to manage IT Service(ITSM). ITIL has been adopted by many organizations as the framework to manage their IT service. There are millions of practitioners worldwide with ITIL skills and capabilities. IT is important to keep in mind that ITIL is a set of best practices and not a standard, so organizations are free to adopt ITIL framework as is applicable or valuable to them. Advantages of adopting ITIL for your organization are immense. Therefore, all scale and size (Small , medium, Large) organizations all over the world use ITIL to help them improve the value of their services. The few important benefits of adopting ITIL are:  ITIL creates stronger alignment between IT and the business Improves service delivery and customer satisfaction Reduces costs with improved use of resources Provides Greater visibility of IT costs and assets A Brief History of ITIL:
Read more

Tracking and Communicating Progress in Agile

Information radiators are meant to display information at a public place so that the information can be noticed by as many people as possible without making a conscious effort to do so. The idea of information radiator was invented by Alister Cockburn, who was a big believer in effective and timely communication. Information Radiators should display the current information about the project whatever is critical for the team to learn. It could include Schedule, tasks, issues, progress etc. The Most common forms of Information Radiators are ·         TaskBoards or Kanban Boards ·         Big Visible Charts such as BurnDown Charts ·         Street Lights and Lava Lamps Characteristics of Information Radiators which make the Information Radiators work ·         Simplicity : The information Radiators should be simple to read and understand ·         Stark : Should display the progress and expose problems. Errors should not be masked, instead, they should be used to improve
Read more

Scrum Timebox

Scrum relies heavily on the concept of Timebox. Timebox is setting a fixed time limit to any activity and letting other characteristics such as Scope vary. A time box could be ·           A Meeting ·           A Sprint ·           A Test activity ·           Development Activity ·           Or Practically anything such as you chatting with your friend on social networking site. The fact about timebox is that the time is limited. You can adjust other parameters such as ·           How much you can get done ·           Which item you must prioritize ·           However, deadlines cannot be moved. In Scrum, all the project iterations, meetings must be timeboxed and time limits be respected. This is very important and non-negotiable aspect of Scrum. Lets look at how a timebox actually works. ·           Timebox can be of any duration  - hours, months, years ·           It is essentially a control mechanism to ensure how much time you wish to devote
Post a Comment
Read more