Thursday, 21 August 2014

Benefit Realization in Scrum

Throughout a Scrum project, it is very important to ensure that intended benefits are being realized as originally planned. Strong benefit realization planning and appropriate verification techniques are required to confirm that the project deliverables with benefits and value are being created by the Scrum team members. This ensures full utilization of project resources. Prototype demonstration and functionality simulation are some of the techniques for confirming benefits and value.
A benefit realization plan helps to forecast contribution of individual project to the overall programme. The plan should be an integral part of any project from start to end. Benefit Realization plan helps to track the sustenance of intended benefits even after the end of a Scrum project.
First step towards benefit realization plan is to identify the intended benefits, stakeholders and the outcomes required followed by measurement of realized benefit, allocation of delivery responsibility, prioritization and identification of delivery dates. Prioritization helps to focus on the benefits with more impact.
Revisiting the Benefit Realization plan at predetermined review points helps the team members to decide whether the changes incorporated are still providing the intended benefits. If the answer is no, then the team should take corrective measures. Consensus of team members and their involvement towards the same output will help the team to move ahead in realizing the desired benefit.
A project manager is responsible for helping the customer gain the desired business benefits. However, the truth is that many successful projects have failed to deliver the desired benefits as planned. Working closely with customers can more clearly determine whether the features are adequate and it helps to make sure that the product gets embedded in the organization. Customers might realize the need for additional features; therefore, the development team should be able to accommodate such changes during product development. Meeting customer expectations and interpreting their requirements are key criteria in realizing benefits. It helps to gain more support from customers and stakeholders.
Some of the techniques and methodologies to confirm benefit realizations are carrying out visual presentation, demonstration of prototypes, workshops and training, arranging product release or launches, accommodating change and being creative in finding problem solutions. Change during such approaches must be sustained even after the end and it leads to realize desired benefits. After delivery of every successful project it is very important to ensure that the product or service that was delivered is used or implemented in the organization.



Wednesday, 20 August 2014

Done Criteria

Deliverables from scrum projects, which are potentially shippable, are also referred to as ‘Done’. instituting an honest, collective understanding of ‘Done’ can protect teams and companies from innumerable hours of refactoring, working on tasks which later turn out to be useless, vague communication, and extra work one did not expect to be ‘Done’. Teams struggled to understand when a task, and then a story, was really ‘Done’. The ‘Done’ criteria are established while creating the prioritized product backlog. While Acceptance Criteria are distinctive for each individual User Story, Done Criteria are a set of guidelines that are valid for all the User Stories in a given Sprint. Product Owners should build ‘Done’ criteria specific to a project and manage it over time.During Sprint Planning, the team has a point of reference as to what it means to be ‘Done’. Good Scrum teams target an established prioritized product backlog where User Stories are well estimated and ‘Done’ criteria are very clear.

Generating and circulating the ‘Done’ criteria is not enough. A ‘Done’ criterion is not generated once, covered up in a document, and seen for a second time under no circumstances.  Teams are duty-bound to plan time in the course of Retrospective Sprint Meetings to examine their ‘Done’ criteria from time to time and decide whether there are prospects for enhancement or change.  Nevertheless, one must avoid doing this in every meeting. Too many reviews, too repeatedly, may generatesuspicion about the legitimacy of the current set of ‘Done’ criteria in the eyes of all the stakeholders. Scrum masters should remember that ‘Done’ Criteria arisefrom various perspectives, the most common being technical and functional. User stories and trialsillustrate ‘Done’ criteria from a technical viewpoint. On the other hand, functional ‘Done’ criteriaare also vital.They can take account ofmatters such as whether the User story has passed its Acceptance Criteria.It serves as a reminder of what it means for the team to be ‘Done’ and acts as a powerful communication tool. A ‘Done’ criterion adds value, and it communicates the value to stakeholders. When stakeholders question, “Are you ‘Done’ yet?” the team can point toward the ‘Done’ criteria and respond clearly where the team is at. Through the ‘Done’ criteria, and through their communication and content refinement, all stakeholders can clearly know that if the team says the product is ‘shippable’, each of its features has met a sequence of necessary criteria that isobligatory for such an action. When anyone in the Scrum team says ‘Done’, it will mean precisely what is put out in the ‘Done’ criteria. 

Tuesday, 19 August 2014

Why should we adopt Scrum?

Before knowing why the information technology industries are adopting scrum in a big way, it is important for us to ask the following questions.
1. Why does your organization need to adopt scrum and why is it better than the traditional project management methodologies like PRINCE2 & ITIL?
2. Why scrum looks just the opposite of the traditional project management methodologies?
In the fast ever changing environment, where the requirements changes thick and fast through the project lifecycle adopting a traditional project management is ever difficult. With so much of R & D being done for various products it’s clear that the change needs to be adapted as soon as you realise it.  In traditional methodologies, change is not accepted easily. It has to go through formal change and amendments. Scrum adopts changes as part of the project and is open for change whenever it comes and the approach followed is actually a "holistic approach" for development. It is actually an approach adopted from US rugby. It is also famously called the "rugby approach" as the team collectively moves together in the field to reach its goal and you would need multiple goals to succeed. Similarly in scrum each goal is equated to a sprint and each sprint should contain a potential shippable output.
Scrum is an empirical process and scrum follows a process of inspecting first and then adapting. Shorter the sprint length the better the inspection and better chances for you to adapt to the changes and fix issues early. Scrum is time boxed to 2-4 week sprints (nothing but phases of the product lifecycle) and though every sprint should have a potentially shippable product, you would only be able to release a product to the customer in 3-4 sprints.
Like in rugby where in the team has a small huddle before the ball is back in play, where the captain motivates the team, in scrum it is the scrum master who will facilitate a daily stand up meeting called "daily stand up", this is a 15 minute meeting every day held at the start of the day to figure out where they are currently and also pick up the list of tasks to be done for the day which are also called backlog.
Scrum has three roles:
·         Product Owner
·         Scrum Master
·         Scrum Team
The maximum allows scrum team size is 8. If your team is bigger than you should ideally apply scrum of scrums.
Scrum has 4 artifacts:
Product Backlog - managed by the product owner
Sprint Backlog
Sprint Burndown
Release Burndown


All the other three artifacts are responsibility of scrum master to monitor and facilitate.

Monday, 18 August 2014

Scalability of Scrum& Scrum of Scrums:

It’s a widely accepted fact that Scrum Teams should ideally have six to ten members. This could be the underlying fact that leads to the misconception that the Scrum framework can only be used for small projects. There are a lot of people who say “Scrum can be used to improve the team productivitybut is not scalable”. In fact, it can easily be scaled for effective use in large projects. Multiple Scrum Teams can be formed to work on the projectwhere the Scrum Team size exceeds ten people. The Convene Scrum of Scrums process facilitates coordination among the Scrum Teams, enabling effective implementation in larger projects. Multiple Scrum Teams work in parallel in large projects, making it necessary to synchronize and facilitate the flow of information and enhance communication. The Convene Scrum of Scrums is the process ensuring this synchronization. The various Scrum Teams are represented in this meeting and the objectives are to provide updates about progress, discuss challenges faced during the project, and coordinate activities.

A Scrum of Scrums Meeting is an important element when scaling Scrum to large projects. Typically, there is one representative in the meeting from each Scrum Team—usually the Scrum Master—but it is also common for anyone from the Scrum Team to attend the meeting if required.
There are no set rules regarding the frequency of these meetings. This meeting is usually facilitated by the Chief Scrum Master and is intended to focus on areas of coordination and integration between the different Scrum Teams. The factors determining the frequency are the amount of inter-team dependency, size of the project, level of complexity, and recommendations from the Scrum Guidance Body.

In organizations that have several Scrum Teams working on portions of a project simultaneously, the SoS Meeting can be scaled up another level to what is referred to as a Scrum of Scrum of Scrums Meeting. In this situation, an SoS Meeting is held to coordinate each group of Scrum Teams working on portions of a related project and then a Scrum of Scrum of Scrums Meeting may be held to coordinate and integrate projects at a higher level. Teams have to carefully evaluate the benefits of having Scrum of Scrum of Scrum meetings, as the third layer adds a significant amount of logistical complexity.This meeting is conducted at predetermined intervals or when required by the Scrum Teams.




Sunday, 17 August 2014

Time-boxed meetings in Scrum

Scrum treats time as one of the most important constraints in managing a project. To address the constraint of time, Scrum introduces a concept called ‘Time-boxing’ which proposes fixing a certain amount of time for each process and activity in a Scrum project. This ensures that Scrum Team members do not take up too much or too little work for a particular period of time and do not expend their time and energy on work for which they have little clarity. Some of the advantages of Time-boxing are as follows:

· Efficient development process
· Less overhead
· High velocity for teams

Time-boxing can be utilized in many Scrum processes, for example, in the Conduct Daily Standup process; the duration of the Daily Standup Meeting is Time-boxed. At times, Time-boxing may be used to avoid excessive improvement of an item (i.e., gold-plating). Time-boxing is a critical practice in Scrum and should be applied with care. Arbitrary Time-boxing can lead to de-motivation of the team and may have the consequence of creating an apprehensive environment, so it should be used appropriately.

The following meetings are listed in the guide to the Scrum Body of Knowledge - 

· Sprint—A Sprint is a Time-boxed iteration of one to six weeks in duration during which the Scrum Master guides, facilitates, and shields the Scrum Team from both internal and external impediments during the Create Deliverables process. This aids in avoiding vision creep that could affect the Sprint goal. During this time, the team works to convert the requirements in the Prioritized Product Backlog into shippable product functionalities. To get maximum benefits from a Scrum project, it is always recommended to keep the Sprint Time-boxed to 4 weeks, unless there are projects with very stable requirements, where Sprints can extend up to 6 weeks.

· Daily Standup Meeting—The Daily Standup Meeting is a short daily meeting, Time-boxed to 15 minutes. The team members get together to report the progress of the project by answering the following three questions:
1. What did I complete yesterday?
2. What will I complete today?
3. What impediments or obstacles (if any) am I currently facing?
This meeting is carried out by the team as part of the Conduct Daily Standup process.

· Sprint Planning Meeting—This meeting is conducted prior to the Sprint as part of the Create Sprint Backlog process. It is Time-boxed to eight hours for a one-month Sprint. The Sprint Planning Meeting is divided into two parts:

1. Objective Definition—During the first half of the meeting, the Product Owner explains the highest priority User Stories or requirements in the Prioritized Product Backlog to the Scrum Team. The Scrum Team in collaboration with the Product Owner then defines the Sprint goal.
2. Task Estimation—During the second half of the meeting, the Scrum Team decides “how” to complete the selected Prioritized Product Backlog Items to fulfill the Sprint goal.
At times, the Task Planning Meetings (conducted during the Create Tasks process) and the Task Estimation Meetings (conducted during Estimate Tasks process) are also referred to as Sprint Planning Meetings.

· Sprint Review Meeting—The Sprint Review Meeting is Time-boxed to four hours for a one-month Sprint. During the Sprint Review Meeting that is conducted in the Demonstrate and Validate Sprint process, the Scrum Team presents the deliverables of the current Sprint to the Product Owner. The Product Owner reviews the product (or product increment) against the agreed Acceptance Criteria and either accepts or rejects the completed User Stories.
· Retrospect Sprint Meeting—The Retrospect Sprint Meeting is Time-boxed to 4 hours for a one-month Sprint and conducted as part of the Retrospect Sprint process. During this meeting, the Scrum Team gets together to review and reflect on the previous Sprint in terms of the processes followed, tools employed, collaboration and communication mechanisms, and other aspects relevant to the project. The team discusses what went well during the previous Sprint and what did not go well, the goal being to learn and make improvements in the Sprints to follow. Some improvement opportunities or best practices from this meeting could also be updated as part of the Scrum Guidance Body documents.