Wednesday, 17 September 2014

How marketing as a business function can benefit from Scrum

Scrum as an Agile methodology is currently most popular in IT development teams. However, that does not mean that it cannot be effectively used in other domains. In fact, as an Agile methodology of managing projects, it can be used wherever people work on projects on a regular basis. It can be used in a particular division of a company – like new product development in an automobile company, and can also be used in a particular function of a company – like marketing. This article will highlight how Scrum methods can be used very effectively to manage marketing projects.
Marketing as a function revolves around projects. Marketing professionals work on a variety of projects – ad campaigns, email campaigns, product prototyping, market research etc. More time is spent on projects rather than operational activities. Hence, Scrum can be especially beneficial for marketing teams.
Let’s say the marketing team is tasked with the project of launching a new car model. How can it use Scrum? Well, it actually is quite simple (one of the basic objectives of Scrum – to keep it simple). You start off with stating the project vision – launching the car in a defined area, say, the state of California. Then you need someone to spearhead the whole project – the Scrum Master. He/she will decide who all will be part of the Scrum team. These have to be people who will actually be doing the various tasks in the project and not the ones who simply have an interest in the project.
So now you have the people who will be working on the Scrum project. What next? The team needs to understand the customer requirements. These are defined in the form of User Stories. In our case, two of the user stories might be ‘I need to test drive the car before I buy it’ and ‘I need to know all its performance specifications’.
The User Stories are approved and entered into what is called the Prioritized Product Backlog. It is the master document which guides the team in the project. It contains the User Stories and the tasks which are required to fulfill the requirements for each of the user stories. So in our example, the first User Story about test drives will include tasks like ‘Decide number and variants of test cars needed’, ‘Brand the test cars’, ‘Create a test drive feedback form’, ‘Decide on the tasks to be performed by the salesperson before the test drive’, etc. It then decides on a Release Planning Schedule which lays out the schedule of shipping out completed deliverables to the customers. The team then estimates the time required for the various tasks. Based on the above, a collective decision is taken on which all tasks will be taken up in the first round – called Sprint in Scrum. A Sprint duration can vary from a week to a few weeks.
The team then works on completing the tasks in a particular Sprint. To ensure that things are on track, the Scrum team has a Daily Standup Meeting which is time-boxed to normally 15 minutes to half an hour, in which all the members stand around and discuss the status of the different tasks. Tasks are entered in post-it notes and stuck on to a whiteboard with 3 columns – ‘To be done’, ‘In Process’ and ‘Completed’.  The team then works on the tasks from the first column to the third column. At the end of a Sprint, when the team has hopefully completed all the tasks, a Sprint Review Meeting takes place where the team discusses what went right and what are the improvement opportunities. At designated points in time as laid out in the Release Planning Schedule, the team ships out completed deliverables.
This process continues till all the deliverables and tasks are completed in the Scrum project. The high level of involvement and communication involved in the Daily Standup Meetings is the key to an effective implementation of Scrum. Thus, by following the above process, marketing teams can ensure speedy completion of projects with high quality outputs without getting bogged down by a lot of documentation and processes.
Note: The Scrum specific terms used in this article are as per the Guide to the Scrum Body of Knowledge (SBOKTM)

 To know more click on: http://www.scrumstudy.com/blog/

Thursday, 4 September 2014

How Scrum framework minimizes risks (threats) in projects?

Every project, irrespective of scale and size, is subjected to risk. Even a smallest of project involves some amount of risk. This is one of the unique characteristics of a project. So, when we work on a project, we do risk management side by side. ‘Risk’ often has a negative connotation and we usually think risks are bad. But in project management it is described as “an uncertain event which if happens will have a positive or negative impact on the project objectives.” So, we try to maximize the impact and probability of positive risks (also called as ‘Opportunity’) and try to reduce or remove the negative risks (also called as ‘Threat’). In project risk management, we do undertake different activities to manage different types of risks based on the probability, proximity, effect and impact of the risks. Let’s focus on the negative risks in this article. Projects are usually riskier at the beginning of the project because of amount of uncertainties involved. Many a times, the customer does not have clear ideas about the requirement which multiplies the uncertainties. ‘Scrum’ framework of managing project is extremely suitable in this scenario. Being an Agile, iterative process, the Scrum framework inherently minimizes risk. The following Scrum practices facilitate the effective management of risk:
  1. 1.    Flexibility reduces business-environment-related risk
Risk is largely minimized in Scrum due to the flexibility in adding or modifying requirements at any time in the project lifecycle. This enables the organization to respond to threats or opportunities from the business environment and unforeseen requirements whenever they arise, with low cost of change as compared to traditional project management methods.
  1. 2.    Regular feedback reduces expectations-related risk
Being iterative, the Scrum framework gives ample opportunities to obtain feedback and set expectations throughout the project lifecycle. This ensures that the project stakeholders, as well as the team, are not caught off guard by miscommunicated requirements.
  1. 3.    Team ownership reduces estimation risk
The Scrum Team estimates and takes ownership of the Sprint Backlog Items, which leads to more accurate estimation and timely delivery of product increments
  1. 4.    Transparency reduces non-detection risk
The Scrum principle of transparency around which the framework is built ensures that risks are detected and communicated early, leading to better risk handling and mitigation. . Moreover, when conducting Scrum of Scrum Meetings, Impediments that one team is facing currently can be deemed a risk for other scrum teams in the future, and that should be recognized in the Updated Impediments Log.
  1. 5.    Iterative delivery reduces investment risk
Continuous delivery of value throughout the Scrum project lifecycle, as opposed to the product being delivered at the end of the project as in traditional project management methods, reduces investment risk for the customer.
Reference: A Guide to the Scrum Body of Knowledge (SBOKTM Guide) by SCRUMstudy

To know more click on : http://www.scrumstudy.com/blog/how-scrum-framework-minimizes-risks-threats-in-projects/