Transition From V-Model ToScrum Methodology

Table of Contents

1. Introduction

1.2 Scope of the report

1.3 Brief description of the company

1.4 Situation that causes methodology transition

2. Transition analysis

2.2 Consideration

2.3 Transition challenges

2.3.1 Using scrum without proper knowledge

2.3.2 Residue from old methodologies

2.3.3 Evaluating agile implementation

2.3.4 Misunderstanding process

2.3.5 Changing team membership

2.4 Transition benefits

3. Test integration phase

3.1 Planning meeting

3.2 Execution of sprint tasks

3.3 Daily stand-up

3.4 Review meeting

3.5 Retrospective meeting

4. STLC activities in scrum based SDLC

4.1 Fundamental test process

4.2 Test implementation and execution

4.3 Evaluating exit criteria and reporting

4.4 Test closure activities

5. Future work

6. Conclusion

1. Executive Summary

 BL (British Library) which is national library of UK. Millions of documents and data are stored in British library. The aim of this report is to find out the challenges which are involved during the transition from v-model to agile scrum. Firstly, BL need to know what are the benefits, risk analysis, consequences of the system etc. Communication and lack of trust between the team members may lead to organization failure. During transition process team members should have proper knowledge of the scrum methodology to avoid dependency.

2.1 The aim and the objective of the report represented

The aim of the BL is to check the transition process from v-model to scrum methodology and differentiate the key difference between the v-model and scrum method. The main objective of BL will look after is what were the challenges faced, risk analysis, transition benefits, what were the consequences faced during the transition.

2.2 Scope of the report

BL main aim is to analyse the project challenges during transition, benefits of scrum, upcoming work and following risk analysis and making team work together for the betterment of the company.

2.3 Brief description of the company

BL (British Library) is the national library of the United Kingdom. BL work is supported by more than 2000 expertise staff and it is linked with other organizations worldwide. BL stores millions of documents. To store millions of documents BL need vast database system to access the system. BL follows v-model to develop the software; software needs to run on different platform where BL is facing different problems with v-model which is more time consuming. To overcome the problems BL decided to transit from v-model to scrum methodology.

2.4 Situation that causes methodology transition

 Company faced high failure in process of testing because software running on multiple platforms. To deal with each consumer requirement it is difficult and more time consuming for the organization. Due to parallel approach of the v-model process so it was difficult for the BL to understand the requirements of the customer.

3.1 Risk Analysis

BL adopting scrum the main risk is not having appropriate knowledge about the method. Lack of communication between the team members and lack of trust issues between team members may lead to the organization failure.

3.2 Consideration

While moving from v-model to scrum method, to gain confidence communication between team members is essential. Proper knowledge as well as proper training for scrum method can have some facts while switching to scrum.

3.3 Transition challenges

3.3.1 Using scrum without proper knowledge

Using scrum methodology without having proper knowledge or information can lead to the organization failure.

Will take more time to complete the expectations of the customer.

Due to lack of confidence, knowledge, and trust can lead to organization failure. (challenges in adopting scrum, 2008)

3.3.2 Residue from old methodologies 

Sometimes people may understand the benefits of scrum adoption and tries to implement it genuinely but character of the old process stays with them.

To track the task status retrospective is used instead of looking for learning’s and facing challenges.

Sometimes, teams take too long time to create the backlog product and shift into iterations.

 Sometimes it happens teams are waiting for finalize requirements of the customer. (Common Challenges Faced By First-Time Agile Organizations, 2018)

3.3.3 Evaluating agile implementation

Implementing agile for the very first time BL will faced problem in evaluating the achievement implementation for their agile method.

Parameters are required for agile achievement implementation.

There would be comparison between the organization that how many organization are moved to scrum methodology or how many projects are made by following this methodology.

Stand-ups meetings will be held to ensure and to measure the steps followed by the organization using scrum method are correct or not. (Common Challenges Faced By First-Time Agile Organizations, 2018)

3.3.4 Misunderstanding process

There is great misunderstanding in its daily execution.

People think using scrum method is common to understand but the old traditional method makes it more difficult for the BL organization to understand.

While using scrum there is a deadline for every project and this makes more difficult to understand. (scrum alliance, 2018)

3.3.5 Changing team membership

Agile teams are designed in such a way that they have to face the change.

When the changes happen in the team most of the members of the teams are not used to this change.

This breaks the confidence of the team and disturbs the environment of the organization.

The organization main aim is to keep their team focus full time on their achievement.

Team member’s elimination has its own consequences. Sometimes it might happen that team member simply leave or get fired by the organization because of not performing.(yanado).

3.4 Transition benefits

 3.4.1 Opportunities for improvement

Implementing scrum framework allows for constant opportunity for development.

While using multiple sprints team member are able to get improved common sense whether it’s working for the team or not working.  (top 5 benefits of scrum, 2017)

 3.4.2 Increased team focus

Breaking the general project into shorter and more convenient sprints.

In scrum the entire attention and focus of team member is on the task at hand.

Team member’s main aim is getting through the sprint and not to bother about the results.

And after the completion of the program the team manager and product owner will start verifying the program and then review the work.

After going through various steps the product is considered as fit and ready for shipping.  (benefits of scrum, 2011)

 3.4.3 Improves innovation

Before any product is ready and fit for shipping it has to pass through several stages of process.

Scrum undergoes through the phase known as sprint.

In this process the member of the team will check whatever the requirement of the customer is implemented or not.

And after the completion of the program the team manager and product owner will start verifying the program and then review the work.

After going through various steps the product is considered as fit and ready for shipping.  (benefits of scrum, 2011)

 3.4.4 Fewer mistakes

In scrum client has the opportunity to engage in all meetings during evaluation process.

Scrum works on the priority of the customer with certain “Framework” known as “Sprint”.

The features and items should be placed as per the requirement of the customer which is discussed in the meetings.  (benefits of scrum, 2011)

 3.4.5 Communication. Communication. Communication

Constant communication between the scrum members is what makes agile method looks better. Communicating between the team members and sharing the views between members and can lead to company’s success. (codigodelsur, 2018)

4.1 Planning meeting

The entire scrum team gathers for meeting, where scrum master chooses the user story which is based on the product backlog based on the priority.

The tasks and the efforts are identified by the team members who need to be complete the execution by the user story. (software testing help, 2018)

4.2 Execution of sprint tasks

The real work complete by the scrum team to complete their job and take the user story into the “complete” state. (software testing help, 2018)

4.3 Daily stand-up

Scrum team meets every day for daily report for 15 minutes, to discuss about what work has been done by the team members yesterday, what are the plans for today, is there any roadblock or not.

During this meeting if there is any problem using scrum method the scrum master takes the responsibility to get it resolved. (software testing help, 2018)

4.4 Review meeting

When the sprint cycle ends, there is a meeting of scrum team members and the product owners to check and also to cross verify the stories as per the requirements of the customer.

At the end sprint is stopped and marked as completed. (software testing help, 2018)

4.5 Retrospective meeting

After the review meeting retrospective meeting takes place. Where the team members of scrum meets and discuss about the documents like what go well during sprint, what did not went well in the sprint, what are the lessons learned, what are the actions taken. (software testing help, 2018)

4.6 Release

Delivering the completed sprint to the customer and identify the documents and learned from the problems faced during the sprint. (Scrumstudy, 2018)

5.1 Fundamental test process

To determine company risk and schedule.

Mentioning the scope of testing and test approaches.

Test cases should be design appropriately.

5.2 Test implementation and execution

Plan test execute.

Test results of the documents, and unsuccessful cases for log defects.

Closure defects should be track.

5.3 Evaluating exit criteria and reporting

Before the testing can be done items must be completed.

5.4 Test closure activities

Cycle should be completed based on time, cost, test coverage, quality etc.

Test metrics should be prepared based on the parameters.

Learning out of the project document.

Test closure report should be prepared. (guru 99)

 Figure 2 STLC activities in scrum based SDLC

6. Possible transition consequences

One of the biggest problem BL library would face at the time of splitting the two team into two different geographical zone or two different countries.

Using v-model you don’t need to have proper knowledge of the system, but while using scrum methodology you need to have proper knowledge and have proper training about the system.

 If team members did not have proper knowledge this may lead to organization failure.

Lack of trust issues and communication between the team members may lead to organization failure.  (jie, 2016).

7. Future work

There should be proper training to the team members before adopting Agile Scrum.

The most challenging part for the BL is to adapt and training flexibility in provisions of switching testing responsibilities and timelines.

Organization should be focusing on customer fulfilment and excellence of the goods.

To understand scrum the main aim of the organization should be communication and trust between the team members to avoid organization failure.(jie, 2016)

To sum up, it is concluded how the transition of v-model to scrum methodology takes less time, low cost and efficiency of the method compare to v-model.From transition from one method to another method BL need to have proper knowledge of the system also BL should be knowing benefits and challenges which BL can face while transition process. BL focus should be on customer satisfaction. There is few risk factors that BL needs to work on are “Lack of Trust and Lack of Communication. In scrum line-up tester is the only individual whose crucial aim is testing and feature assurance. While adopting the change group members should have proper information of scrum method.

7. References

challenges in adopting scrum. (2008, december 12). Retrieved from InfoQ: https://www.infoq.com/news/2008/12/scrum-adoption-challenges

Common Challenges Faced By First-Time Agile Organizations. (2018, june 18). Retrieved from knowledgehut blog: https://www.knowledgehut.com/blog/agile/common-challenges-faced-by-first-time-agile-organizations

guru 99. (n.d.). Retrieved from STLC – Software Testing Life Cycle Phases & Entry, Exit Criteria : https://www.guru99.com/software-testing-life-cycle.html

jie, j. l. (2016). industrial case study of transition from v-model into agile scrum in embedded software testing industries.

scrum alliance. (2018). Retrieved from The Top 3 Challenges Companies Face During the Transition to Scrum: https://www.scrumalliance.org/agile-resources/the-top-3-challenges-companies-face-during-the-tra

softwaere testing help. (2018, september 25). Retrieved from Agile Scrum Methodology: Complete Guide for Developers and Testers: https://www.softwaretestinghelp.com/agile-scrum-methodology-for-development-and-testing/

software testing help. (2018, september 25). Retrieved from Agile Scrum Methodology: Complete Guide for Developers and Testers: https://www.softwaretestinghelp.com/agile-scrum-methodology-for-development-and-testing/

yanado. (n.d.). Retrieved from 6 Challenges In Applying Scrum And How To Overcome Them: https://yanado.com/blog/6-challenges-in-applying-scrum-and-how-to-overcome-them/