Requirement Gathering Techniques.

Before starting with techniques of gathering requirements, let us understand what is Requirement and its types.

What is Requirement?

- A capability that an intended product/software must possess to satisfy the         customers need, objective and goals. Requirement is ‘What’ system should         do (functioning of the system), ‘When’ it should perform those functions and       ‘How’ the system should behave i.e. what and how system should behave in        different conditions.

- A key component of any business project which provides objective ways to         measure the project’s success. 

Types of Requirements:

• Business Requirement: 

- A High-level requirement defining the business’s objectives, goals and vision. 

- Providing the scope of a business need or problem that needs to be addressed    through a specific activity or project.

- Must be defined clearly at high-level.

• Functional Requirement: 

- A detailed breakdown of the Business Requirements explaining how the              system outcome of a project will operate to meet the specified business              requirements.

- It is basically the series of steps that different users will take in the new             system.

• Technical/ Non-functional Requirement:  

-  Pertains to the technical aspects that your system must fulfill, such as                 performance-related issues, reliability issues, and availability issues. 

- Also called as service level requirements or quality of service (QoS)                    requirements.

You can also categorize requirements as:

• Conscious Requirements: stakeholder knows the requirement.

• Unconscious Requirements: stakeholder knows the requirements and thinks it    is obvious and need not have to explicitly mention it. 

• Undreamed requirements: stakeholders does not ask for, either because they think they are not possible or they are new ideas that have occurred to them.

Techniques to Gather Requirements:

When it comes to business requirements gathering, various techniques are available and each technique has its own merits and demerits. Commonly used techniques are:

1 Questionnaires

Questionnaires are much more informal, and they are good tools to gather requirements from stakeholders (dozens/hundreds/ or thousands of people) across geographical areas or those who will have only minor input into the overall requirements. It has a series of questions which helps eliciting information from users. 

Survey- is one of the types of questionnaire. It insists the users to choose from the given options i.e. YES/NO, Agree/Disagree or ratings. A well designed survey gives a significant amount of focused data in a short period of time. It should not be utilized for prioritizing of requirements or features.

 

2 Interviews

One of the commonly used techniques where you have zero chances to satisfy the stakeholders and users’ needs if you do not know their expectations and goals. You also have to understand the perspective of every interviewee, in order to properly address and weigh their inputs. Good Listening skills is the key to get the best results by using this technique.

3 Focus Group & Workshops

A focus group is actually gathering of people who are customers or users representatives for a product to gain its feedback about opportunities, needs, and problems to determine requirements or it can be collected to refine and validate the already elicited requirements. It reveals a wealth of detailed information and deep insight.

Workshops are popularly known as JAD or joint application design and can be efficient for gathering requirements. These are more organized and structured than a brainstorming session where the involved parties get together to document requirements. A workshop with two analysts is more effective than one in which one works as a facilitator and the other scribes the work together.

4 Observation

It covers the study of users in its natural habitat i.e. you work with the user as Shadow. By watching users, a process flow, pain points, awkward steps and opportunities can be determined by an analyst for improvement. Observation can either be passive or active.

• Passive observation- provides better feedback to refine requirements 

• Active observation- works best for obtaining an understanding over an existing   business process.

5 Document Analysis- studying Documentation

Evaluating the documentation of a present system can assist when making AS-IS process documents and also when driving the gap analysis for scoping of the migration projects. Chunks of information are mostly buried in present documents that assist you in putting questions as a part of validating the requirement completeness.

As per the ‘BABoK (Business Analyst Body of Knowledge)’, additional techniques are: 

1 Interface Analysis

Interface for any software product will either be human or machine. It is an elicitation technique that helps to identify interfaces between solutions/applications to determine the requirements for ensuring that the components interact with one another effectively i.e. requirements needed to integrate software into its new environment.

2 Prototyping

Prototyping can be very helpful at gathering feedback. It comprises of collecting the requirements and building a prototype. It gives an idea to the user about how their system will work and look like and based on the feedback received you can improve the system by adding/amending the requirements on iterative basis until users finalizes it.

3 Brainstorming

It is utilized in requirements elicitation to gather good number of ideas from a group of people. It is used in identifying all possible solutions to problems and simplifies the detail of opportunities. In short, it is all about:

• Idea generation and

• Idea reduction and voting

4 Reverse Engineering

When you do not have the documentation available with you for an existing project then you review the source code to figure out what actually is happening and is called ‘Reverse Engineering’. It will not determine what thing(s) went wrong with the system and what a system must do.

Conclusion: 

You cannot use a single technique to gather the requirements for a project. It is always a combination of multiple techniques. Therefore the usefulness of a technique is determined by its need and the kind of advantages it offers in a particular project.

Asshima Cheetal is a consultant in Systems Plus Pvt. Ltd. Within Systems Plus, She actively contributes to the areas of Technology and Information Security. She can be contacted at:aashima.cheetal@spluspl.com

Project Managment Office

• What is PMO

The Project Management Office (PMO) in a business or professional enterprise is the department or group that defines processes and the same is implemented throughout the organization in true letter and spirit. The PMO strives to standardize and introduce economies of repetition in the execution of projects. The PMO is the source of documentation, guidance and reporting on the practice of project management and execution.

• Why PMO

For years, business units have struggled to deliver projects on time and within budget. But with today’s emphasis on getting more bang for the buck, IT has to rein in projects more closely than ever. That challenge has led S+ to turn to the project management office (PMO) as a way to cut costs and improve on quality of project delivery.

Overview of  the PMO Framework

• PMO Phases

• Stage Name

• Overview

1  PRE-SALES

Pre-Sales is not a part of the PMO Process flow however the input to the Initiation and Planning phase is acquired from the Pre Sales phase. This phase involves a series of interactions with the client to understand the clients business processes, challenges faced, operating environment, budgets, etc. and responding to the same. It is highly recommended that time and resource commitments required to conduct this phase of the project are taken into consideration during the Sales/Pre-Sales phase when the project cost and effort estimation are being worked out. The final output of this phase is the Approved SOW/Contract.

 2  INITIATION & PLANNING

This is the kick-off and planning phase of the project and is a crucial part of project delivery. In this  phase the project management plan and project plan (detailed) are prepared. Resources are identified.  Project Initiation and Closure form is filled in and sent to the Time Live administrator for project  creation and to the PMO for project folder creation and access management. Project Assignment  Review Forms are prepared to identify expectations from each resource.

 3 EXECUTION

This is the phase where the project team starts working on the project activities and deliverable s. The project activities will depend upon the nature of the project (project type) and the process level defined for the project. The actual project activities and deliverable s however may differ from project to project and will completely depend upon the project’s requirements and agreement with the customer.

 4 MONITOR & CONTROL

This phase spans across the entire project cycle starting from the time the project is initiated until its closure. It defines the project management and governance activities for the project. These activities should be carried out as per the frequency defined in Project Initiation and Closure Form/PMP. Risks, issues and constraints are monitored during this phase and are tracked in the RIC Log. Any change resulting in scope, time, cost and resource are evaluated during this process.  

 5 CLOSURE

Project Closure defines the final activities that need to be carried out when the contractual agreement of the project has ended. Ensure deliverable s are as per the SOW and validate the same with a closure note from the customer. This closure note severs as an official sign off from the customer after which an internal sign off needs to be taken from the PMO on completion of internal deliverable s that include lessons learned and customer feedback form. In case feedback form is not received from client then at least two follow-ups done should be demonstrated (email copy, conference call recording, dashboard report etc) to close the project.

6 PMO Training and Induction

PMO group will train users annually to provide PMO awareness. 

All Users will undergo an Internal Certification course.

Effectiveness of training will be evaluated on the basis a test and implementation of the same.

Individuals who qualify in any of the above criteria will be awarded with Certificates.

An induction will be conducted for all new joiners that covers an overview of PMO, Time Live, PMO Service Desk and Systems Plus PMO site

About Author:

Maheshwari Shah is a consultant in Systems Plus Pvt. Ltd. Within Systems Plus, She actively contributes to the areas of Technology and Information Security. She can be contacted at: maheshwari.shah@spluspl.com

Breathing Business: A Nerve to link Customers

In today’s era of innovation and automation, understanding and nurturing customer needs has become more significant. In fact nurturing relationship with your customer will impact success rate of your business. If one is able to build a strong relationship with customer he can definitely acquire better business. 

However there are few factors which are taken into consideration when it comes to actual understanding the customer needs and wants

Transparency: Company – Client - Customer

To build customer loyalty:  Customer satisfaction matters because selling more to existing customers is easier and cheaper than finding and selling to new ones. Loyal customer will tend to buy more and more and eventually recommend your business to others. To gain customers loyalty we need to tell the customer what exactly we are doing for them with reference to any activities such as different offers on different product, membership card schemes for long term customers and their benefits. Parallel to it,

Remember customers in special occasion by sending them greeting cards which in turn build your relation with customer. 

To develop customer confidence: Customer confidence can be gained only if we deliver the required product to the customer. Parallel to it, if the customer is satisfied with the functionality of products what he desired than it will multiply the faith of customer on company and eventually the revenue.

To prevent customer complaints: Once the required project or product or the service is delivered to the client than it doesn’t implies all work has been done. Every project has to be checked under client controlled environment so that implementation as well as maintenance phase can be carried out successfully.

Positive v/s Negative word of mouth - Its impact on Business

Happy customers who get their issue resolved tend to tell other people about their experience. This is a way to significantly influence the word of mouth about your business. Don’t act as a nameless or faceless business; genuinely talk with your customers as a person representing the business. Ensuring all customer concerns are answered in a timely manner with a friendly and personal response.

On the other hand, an unhappy customer tends to tell more people about their bad experience. In fact, 13% of unhappy customers tell over 20 people about their experience. That’s a lot of negative word of mouth which in turn will definitely impact your business as well as create a negative image of your company. 

People before Profit

How much will that affect your business and its reputation in your industry? Customer satisfaction is tightly linked to revenue and repeat purchases. What often gets forgotten is how customer dissatisfaction negatively impacts your business. Diligently acquiring and analyzing customer feedback will help you identify if customers are actually happy with your product or services.

Satisfied customers may also recommend your products or services to other potential customers, increasing the chances for additional revenue and profit.

Deliver the committed

Committed is what that transforms a promise into reality so at the time of deployment make sure all the requirements has been covered in order to deliver an efficient product / application.

Customer delight – the wow factor

In today's business world, speed is essential. If your company delays in responding to customers, you're missing a huge opportunity to capture valuable insights and positive feedback. Don't give your competitors an opportunity to serve your customer better and faster than you can.

1 Always be timely

2 Always listen to your customers.

3 Give customers little things when they don't expect it.

4 Have policies, but always be flexible

5 Tell your customers how you will help them

Retain your customers

It is found that a ‘totally satisfied customer’ contributes 2.6 times more revenue than a ‘somewhat satisfied customer’. Furthermore, a ‘totally satisfied customer’ contributes 14 times more revenue than a ‘somewhat dissatisfied customer’.Satisfaction plays a significant role in how much revenue a customer generates for your business.

Customer satisfaction plays an important role within your business. Not only is the leading indicator to measure customer loyalty, identify unhappy customers, reduce churn and increase revenue; it is also a key point of differentiation that helps you to attract new customers in competitive business environments.

About Author:

Himanshu Suryawanshi is a consultant in Systems Plus Pvt. Ltd. Within Systems Plus, He actively contributes to the areas of Technology and Information Security. He can be contacted at: himanshu.suryawanshi@spluspl.com

Risk Analysis Techniques

Risk: Project risk can be defined as any uncalled event or a condition that, if occurs, impacts at least one of the project objectives. 

Risks can either be positive or negative. 

•  Negative risks are unwanted and potentially can cause serious problems      and spoil the project.
•  Positive risks, on the other hand, has a positive effect on the project such    as increasing the Rate of interest or finishing the project ahead of time.
•  Once the risks are identified, we proceed with their analysis. Risk Analysis  determines which risk factors will potentially have a higher impact on the    project and, therefore, should be managed by the stakeholders correctly.

The various techniques for risk analysis are as under:

1.Brainstorming

It is largely used in formative project planning, which helps in identifying and postulating risk scenarios for any given project. 

Process:
Considered as an effective attempt to help people think creatively in a         group without having a fear of being criticized by others. 

• Each member tries to build on the ideas given in preceding comments. 
• Criticism and disapproving verbal or nonverbal behaviors are not allowed. 
• The main intention is to encourage as many ideas as possible, which in turn, triggers the ideas of others.

Best suited - To identify maximum amount of risks possible in a project, as employees build on each other’s ideas, producing much greater output than they would as individuals.

2.Sensitivity Analysis

This is the simplest form of Risk Analysis. 

Process:

• Analysis of the effect of change of a single variable in a project is done, and a corresponding value is placed for the same in the project. 
• This uncovers uncertainty and risks for that project i.e. the sensitivity of the project is exposed.
• Generally, such type of analysis is performed only on those variables which have higher impact on cost and time to which the project is most sensitive.
• Best suited when attempting to determine the actual outcome of a particular variable, if in case it differs from what was previously assumed. The analyst can determine how changes in one variable will impact the target variable by creating different scenarios.
• For example, an analyst might create a financial model that will value a company's equity (the dependent variable) given the amount of earnings per share (an independent variable) the company reports at the end of the year and the company's price-to-earnings multiple (another independent variable) at that time. The analyst can create a table of predicted price-to-earnings multiples and a corresponding value of the company's equity based on different values for each of the independent variables.

Weakness: 
Variables are treated individually, which limits the combinations of variables to be assessed

3.Probability Analysis

Probability analysis overcomes the limitations of sensitivity analysis by mentioning a probability distribution for each variable, and then assessing situations wherein, any or all of these variables can be modified at the same time. 

This analysis answers 3 questions:

     • What can go wrong?

     • Severity of the potential detriment?

     • How likely it is to occur?

        Best suited when companies have a large amount of data.

4.Delphi Method

A panel of experts arrive at a convergent solution to any specific problem, so as to form a consensus of opinion. This is very useful for probability assessments of large and critical risk impacts related to the future. The first and most important step is to select a panel of people who have experience in the area of issue. 

It is advisable that the panel members should not know each other’s identity and hence the selection process should be conducted at different locations.

The responses along with opinions and justifications, are evaluated and a statistical feedback is given to each panel member in the next iteration. The process is ongoing, until group responses converge to any particular solution.

Best suited - For Business Forecasting as forecasts (or decisions) from a structured group of individuals are more accurate than those from unstructured groups. Also decisions are not biased which keeps any one person from having undue influence on the outcome.

5.Monte Carlo

The Monte Carlo method is simulation by means of random numbers. It is a simple yet powerful way of incorporating probabilistic data. 

Basic steps include:

(a) Define a domain of possible inputs.

(b) Generate inputs randomly from a probability distribution over the domain.

(c) Perform a deterministic computation on the inputs.

(d) Aggregate the results.

Monte Carlo method determines best case, most-likely, and worst-case estimates for any given scenario.

Example: 

Consider creating Most-Likely, worst-case and best-case estimates for the duration of a project. For each of the above mentioned scenarios, the project manager lists out the probability of occurrence.

• Most-likely scenario: Duration will be of three days (70% probability), but it can also be completed in two days (10%) or even four days (20%)
• Worst-case scenario: 60% probability of taking six days to finish, a 20%   probability each of being completed in five days or eight days.
• Best-case scenario: 80% probability to complete in four days, 5% probability to complete in three days and a 15% probability to complete in five days
• A series of simulations are performed on the project probabilities using the Monte Carlo Analysis. The simulation is to run for a thousand odd times, and for each simulation, an end date is noted.
• Once the analysis is completed, there would be no single project completion date. Instead a probability curve is formed which depicts the likely dates of completion and the probability of attaining each.
• With the help of this probability curve, the project manager informs the senior management of the expected date of completion. The project manager would choose the date with a 90% chance of attaining it.

Best advised - To use the Monte Carlo simulation to analyze the likelihood of meeting objectives, given project risk factors, as determined by our schedule risk profile. It is very effective as it is built on evaluation of data numerically and no guesswork is involved.

About Author:

Geetika Varma is a consultant in Systems Plus Pvt. Ltd. Within Systems Plus, She actively contributes to the areas of Technology and Information Security. She can be contacted at: geetika.varma@spluspl.com

The Agile - Scrum Framework

Scrum is framework which is based on agile principles, a framework that handles simple, complicated and complex software development. Scrum is based on continuous improvement in product and process. Scrum deliver software frequently (value), it showcase the hidden problems in systems development. In scrum project move forward with series of iteration that are called Sprints. Each sprint size is typically two to four weeks long. It is based on inspect and adaptive cycle. Produce product incrementally and iteratively, thus reduce risk and enhance visibility.

Scrum has simple roles, activities and artifacts.

Scrum Roles:   Below are the roles in Scrum

1 Product Owner,   2 Scrum Master, 3 The Team

1 Product Owner

•  Product Owner (PO) is client's representative, define features of product and decide release date and content
• Priorities features according to market value and be responsible for the profitability of product
• Accept or reject work items

2 Scrum Master

• Coach for scrum team , Enacting scrum values , Ensure team's productivity
• Build winning team, Apply agile principles and make system effective.

3 Team

• 5-9 Members team (Developer , Tester) , Self-organizing, High performance team
• Build winning product, Work collaboratively and share responsibilities, Cross functional team.

Scrum Activities:
1. Sprint Planning
2. Daily Scrum
3. Sprint Review
4. Sprint Retrospective
5. Product Backlog Refinement

1 Sprint Planning:
       Goal: Team to plan and agree on backlog items they can complete and confirm the tasks required        to support acceptance

Product owner present the backlog items in priority order for review

• Review and clarify user Backlog items/stories
• Breakdown larger stories and each story into task and acceptance criteria
• Task are estimated in hours by team, Developer and tester assigned to task
• Process continue until all available hours are used for the sprint.
• Output of sprint planning is be Sprint backlog, Estimated tasks etc.
• Duration: 4 Hours for 2 weeks sprint , Who: Scrum Team, Scrum Master, PO, When: Beginning of the Sprint

2 Daily Scrum:
Goal: Plan for the day, Inspect and Adapt daily towards reaching the sprint goal.
Description:

• Daily development Team standup for 15 minutes in circle and talk only on three points
• What I did since last daily scrum meeting?
• What I am planning to work on today?
• Impediments (Issue/blocker) if any?
• Scrum master protect the team and facilitate for being effective.
• This give an opportunity to team to inspect and adapt daily on the sprint goal.
• Who: Scrum Team, Scrum Master, When: Daily throughout the sprint , Duration: 15 minutes maximum

3 Sprint Review:
Goal: Get feedback on product development. Inspect and adapt on the product feature.
Description:

• During this meeting team demonstrate 100% completed work.
• Scrum master facilitate the environment.
• In case of new request, Product owner (PO) note and updates the product backlog as required.
• Product owner is final decision maker on acceptance.
• Duration: 2 hours for a 2 week sprint, Who: Scrum Team, Scrum Master, PO, Stakeholders, When: Last day of sprint

4 Sprint Retrospective:
Goal: To inspect and adapt to become more effective and efficient on process, people, culture aspect.
Description:

• Participation in the discussion to inspect and adapt as scrum team.
• Scrum master play vital role in sprint retrospective, Scrum master bring in the culture of openness, trust and respect as people discuss the improvement areas, facilitate and focus on improvement and changes that pointing fingers at others.
• This is platform to scrum master to help team resolve ineffectiveness in the systems
• Inspect and Adapt: Try everything that makes sense, reject things that didn’t work even after repeated trails. Shape your culture, process and practice.
• Duration: 2 hours for a 2 week sprint, Who: Scrum Team , When: Last day of sprint

5 Product Backlog Refinement:
Goal: Keep product backlog items ready, uncertainty to certainty
Description:

• Product owner provide clarity on each product backlog item (All uncertainty clarified into certainty )
• Product owner Update product backlog. 100% be present and involve all team members
• Team understand, carefully listen to need of product owner, understand the acceptance criteria. Help product owner to order the backlog.
• Duration: 1-3 hours depending on the team’s need. , Who: Scrum Team, Scrum master, PO, When: Continuous process, in between the sprints.

Scrum Artifacts:
Below are Scrum Artifacts.
1) Product Backlog,   2) Sprint Backlog, 3) Product Increment

1 Product Backlog
This is an ordered list of ideas for the product, which can come from the product owner, team members, or stakeholders. A description and estimate of effort complement each product backlog item.

The product backlog is ordered to maximize the value delivered by the Scrum team. The development team’s work comes from the product backlog, and nowhere else. Every feature, enhancement, bug fix, documentation requirement, every bit of work the team does comes from a product backlog item.

The product backlog may begin as a large or short list. Typically it begins short and becomes longer and more defined as time goes on. Product backlog items slated for implementation soon will be "refined," which means they will further clarified, defined, and split into smaller chunks. Though the product owner is responsible for maintaining the product backlog, the development team helps produce and update it.

2 Sprint Backlog
The sprint backlog is the list of refined product backlog items chosen for development in the current sprint, together with the team's plan for accomplishing the work. It reflects the team's forecast of what work can be completed. Once the sprint backlog is established, the development team begins work on the new product increment.

3 Product Increment
Every sprint produces a product increment, the most important Scrum artifact. A product Increment is the "goal line" for each sprint and, at the end of the sprint, it must:

• Be of high enough quality to be given to users
• Meet the Scrum team's current definition of done
• Be acceptable to the product owner

Scrum Information Radiators:

Task boards:

• Task boards allows transparency, display what is the live status of the teams work and focus area
• Simple task board has backlog , To-do, in progress and done status
• There are various format
• Team design their best “Information Radiators” that helps them in self-organizing

Burndown Chart:

• For current sprint, it shows  the total estimated work remaining for the entire forecasted sprint backlog against time
• Updated by team , regularly  and continuously
• Independent of the work, it represents total remaining estimated time to market to achieve sprint goal

About Author:

Kshitij Yelkar is a consultant in Systems Plus Pvt. Ltd. Within Systems Plus, He actively contributes to the areas of Technology and Information Security. He can be contacted at: kshitij.yelkar@spluspl.com

Customer Relationship Management

All the companies want to increase their rate of sales and quality of their services/products continuously to higher and higher points. 
Hence, nowadays, it is almost impossible to unlink CRM and success of the business.

Now, let’s understand what exactly is Customer Relationship Management? 

Peter Drucker rightly said “The purpose of a business is to create and keep a customer.” this is exactly what CRM is all about!

Customer Relationship Management (CRM) is an approach to manage a company’s interactions with current and future customers. It often involves use of technology to organize, automate, and sync sales, marketing, customer service and technical support.

Broadly, it’s the relationship between the organization and its customers. Customers are the backbone of any organization, be it a global corporation or a small trader with a handful of regular customers.

Successful organizations make use of three basic steps to build customer relationships:

• Decide on mutually satisfying goals 
• Set up and maintain customer rapport
• Generate positive feelings in the organization as well as for the customers

1 CRM conditions
To have a good CRM, we need to consider set of conditions such as- wants and needs of both the parties:

• For organizations- Make profit to survive and grow
• For customers- Good service, quality products and an acceptable price

2 Need of CRM

• To increase profit- By providing better services to customers than our competitors
• Reduced costs, wastage, and complaints
• Reduced staff stress as services and relationships improve 
• Instant market research, as customers give us direct and constant market feedback on our products, services and performance, far better than any market survey.

A good CRM grows our business due to following reasons:

• Customers stay with us longer
• Referrals to new customers increase, from increasing numbers of satisfied customers 
• Organization’s service flows are more efficient as teams work happily 
• Organizations should aim to be more customer-centric. 

Let’s understand this better with a simple example: 
Previously, the old viewpoint in the industry was: 

• ‘Here’s what we can make – who wants to buy our product?’

But now, the new viewpoint in the industry is:

• ‘What exactly do our customers need?’ and
• ‘What needs to be done to be able to produce and deliver it to our customers?

'This is a significant change of pattern in terms of how we look at our business activity.

3. Benefits of effective CRM
There are significant business benefits that flow from an effective, integrated CRM approach. These include:

• Costs reduce (effective and efficient working)
• Customer satisfaction
• Growth in numbers of customers
• Maximization of opportunities (due to referrals, increased services, etc.)
• Improved access to a source of market and competitor information
• Highlights poor operational processes
• Profitability and Sustainability

Basic underlying principle to a good CRM:

• Organizations who have momentary relationships with customers consequently, have to shell out a lot of money in finding new customers.
• Hence, relationships with customers should be – 
• Continuous
• Cooperative, and
• Made for the long term.

The cost of keeping existing customers is a tiny fraction compared to the cost of acquiring new customers!


About Author:
Geetika Varma is a consultant in Systems Plus Pvt. Ltd. Within Systems Plus, She actively contributes to the areas of Technology and Information Security. She can be contacted at: geetika.varma@spluspl.com

Application Support Life Cycle

Following phases of application life cycle:

     1. Service Strategy

     2. Service Design

     3. Service Transition

     4. Service Operation

     5. Service Improvement

Service Strategy

Organization makes a plan to manage costs and risks associated with starting any new service or changed service. Within this plan, organization performs the following:

· Set Up Expectations For Serving Customer

· Budget & Financial Performance Plan

· Opportunity Analysis

· Operational Process Requirements 

    Service Design

Based on requirements obtained in the Service Strategy stage, new services are required to be designed and developed. For example, make a service according to client agreed on expectation of service such response time of issue and change request. Following things are included in design phase:

· Statement of Work (SOW)

· Service Level Agreement (SLA)

· Operational Process Requirements

    Service Transition

During transition for new or changed service into operation phase, make a plan to set the operation capacity and structure of application support team. In this plan, define a set of work processes for team to teach how work will be organized and managed. For example, plan how many people will be part of the support process; give them idea about work process etc.

Following things are included in the plan:

· Team Operations Documents

· Application Knowledge Documents

· Operational Work Processes

    Service Operation

The application support team needs to perform day-to-day operational activities in order to provide a service as per statement of work agreed in a service level agreement. Service measure with the help of following reports:

· SLA Report

· Work Event Status Report

· Time Usage Report

· Resource Performance Report

    Service Improvement

Once service set up and it is on track, needs to improve process in order to improve processes efficiency and reduce cost. Based on status reports, check the gaps and improvement area and try to fill it. For example, make optimum use of resources resulting in improved efficiency and reduced cost.

Application support life cycle provides a roadmap for improving and implementing Application Support in terms of processes, outcomes

About Author:

Deepak Borole is a consultant in Systems Plus Pvt. Ltd. Within Systems Plus, he actively contributes to the areas of Technology and Information Security. He can be contacted at: deepak.borole@spluspl.com

An Insight to Supply Chain & Models

A basic supply chain is the flow of raw materials and services from receiving the raw materials to the manufacturing &processing of the same till the final products are obtained.Thisprocess involves the movement of raw material,work in progress inventory and finished products. A simple supply chain concept would be- The raw material is taken to the factory where it is stored in the warehouse, sent for manufacturing, again stored in the warehouse, transported to the distributors and the movement of these products continue till they reach the end user/customers.

Importance of Supply Chain:

Supply chain not only plays an important role in organizational activities, but also plays a vital role in delivering the goods to the end user through multiple points of processing. It helps the organization to cut inventory costs, provides multiple sources of information through various channel partners and helps in giving an effective and efficient customer service which results in customer satisfaction. The degree of customer satisfaction helps in measuring the success of any supply chain qualitatively

Different types of supply chain models:

1. Build to order model

2. Continuous replenishment model

3. Integrated make-to stock model

4. Channel assembly model

    1. Build to order model:

Buildto order model aka (BTO), which is user specific, which means customer gives his customized requirement for the product and the company immediately starts assembly for producing the goods. But the company needs to be accurate on design and quality of product. The advantage of this is the consumer gets the rapid delivery of the product with the good feeling of possessing the customized product & it is also efficient for the company too as they are producing the goods only when required by the consumer.

    2. Continuous replenishment model:

According to this model there is a continuous delivery of the raw material from the supplier so as to occupy the space of those ones which has been used, but for this a close watch on the quantity is needed so as not to increase the cost sharply which could result in the collapse of the supply chain.

    3. Integrated make-to stock model:

This type of model focuses on, to stock the products which are in trend or are in demand from the customers, so as not to run out of stock of those products or goods. For this it needs a good forecast so that it can meet the exact balance between the production and consumption.The disadvantage of this model is that it is depended heavily on the accuracy of forecast.

    4. Channel assembly model:

In the channel assembly model all the components of products are gathered and assembledas it moves through the production line. This is achieved through the collaboration of all the outsourced suppliers and involves the transportation of the products. An example for this can bethe assembling different computer parts to construct the computer.

Thus we can say supply chain is a vast field and has different models which can be adopted by the companies according to their need, so that it allows them to be more efficient in terms of its production, cost and quality.

About Author:

Rohan Bhardwaj is a consultant in Systems Plus Pvt. Ltd. Within Systems Plus, he actively contributes to the areas of Technology and Information Security. He can be contacted at: rohan.bhardwaj@spluspl.com