'Continuous Quality Improvements – A Journey Through The Largest Scrum Project In Norway' by Kristina Lassen Tangen
Upcoming SlideShare
Loading in...5
×
 

'Continuous Quality Improvements – A Journey Through The Largest Scrum Project In Norway' by Kristina Lassen Tangen

on

  • 367 views

In this presentation you will learn about how the testing process and continuous quality improvements are aligned to the scrum process in a large software project. We hope that our hands -on ...

In this presentation you will learn about how the testing process and continuous quality improvements are aligned to the scrum process in a large software project. We hope that our hands -on experience will give you inspiration on how to tailor the test process in an agile environment. The project has been running for more than two years, with six successful releases to end users. We would like to share our experiences with managing test processes in a large scrum project – our do’s and don’ts, our success stories and also our lessons learned. The project is the largest scrum project in Norway to date.



The project scope is to implement system support for managing a new pension reform for all inhabitants in Norway that are members of the pension fund, and replacing existing system due to outdated technology. Approximately 750 000 project hours will be spent and between 100-180 people are involved in the project: thirteen scrum teams, plus two project management and acceptance testing teams, and one business expert team. Each scrum team contains all the knowledge and expertise needed for developing high quality software: Scrum master, business expert, technical architect, UX designer, developers, build/deploy responsible, and of course, dedicated test resources.



Each software delivery in this project contains five sprints. Each sprint is three weeks, followed by acceptance testing before the delivery is shipped. Test driven development is used in all levels of development, from unit tests all the way up to functional system testing. All test levels up to system integration testing is performed during the development sprint by the scrum teams. We tried to automate UI tests, but this was not successful. However, tests in all other levels are successfully automated, and after each delivery, a fully automated regression test suite is shipped with the code.

Statistics

Views

Total Views
367
Views on SlideShare
367
Embed Views
0

Actions

Likes
0
Downloads
4
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

'Continuous Quality Improvements – A Journey Through The Largest Scrum Project In Norway' by Kristina Lassen Tangen 'Continuous Quality Improvements – A Journey Through The Largest Scrum Project In Norway' by Kristina Lassen Tangen Presentation Transcript

  •  www.steria.no© SteriaTest process aligned to scrum– Experiences from project PERFORMKristina L. TangenTest Manager – Steria’s deliveries to PERFORM
  •  Facts about PERFORM The largest and most importantproject ever for the State Pensionfund Government funded About 750 000 project hours spentand 100-180 persons involved Implements system support formanaging new pension reform Replacing legacy system due tooutdated technology Agile development methodology -Scrum
  •  OrganizationCustomerSubprojectBusinessSupplierSubprojectdevelopmentRoll-outBusinessmodeling teamApplicationarchitect teamMaintainingEnvironmentsteamAcceptancecriteriaFunctional test Approval testAnalysis anddesignSPK Acceptance testAccenture DeploymentSteriaProject director - Project managerSubprojectArchitectureSubprojectTest
  •  Scrum teamScrum masterTechnicalarchitectTestresponsibleDevelopers/testersUsability expertFunctionalarchitectProductOwner
  •  Project lifecycle 3 weeks iterations 3 deliveries a year 4 years duration
  • Development cycleResponsibility: Development teamsTest Strategy - PERFORM Unit test Integration test –Continuous integration Functional System test Functional Integration test Approval test Acceptance test Production test
  • Acceptance criteriaIteration n - 1 Iteration n Iteration n + 1Execute System Integration testsTest process - developmentDefine andexecuteunit andintegration testsDefine and refinefunctional testconditionsDefine andexecuteFunctionalsystem tests
  •  Unit testing and integration testing Whitebox testingtechniques Automated tests Tools: Junit, Flexunit,DBunit, Jmock andchecklists Continuous integration Hudson
  •  Functional test - System testing System testing is performed by the developmentteams All user stories have functional test criteria At least one functional test per user story Automating tests should be considered Tools used on this level: Fitnesse and Quality Center
  •  Functional test – System testing Test conditions logged inQuality Center asrequirements All test conditions covered byat least one functional test All test conditions approvedby a business analyst
  •  Test automation – Functional test
  •  Functional Integration testing Planning and executing these tests is a team responsibility Planning takes place in the iteration before the test is executed Continuous Functional Integration testing during the whole developmentcycle Development and test environments are separatePlan acceptancecriteriaIteration n - 1 Iteration n Iteration n + 1Run System IntegrationtestsWrite and rununit andintegration testsWrite and modifyfunctional testconditionsWrite and runFunctionalsystem testsPlan Systemintegration test
  •  Controlling test quality After each iteration a quality checkof delivered user stories takes place Test:▬ Test coverage▬ Functional tests – both positive andnegative (destructive) are performed▬ All code delivered is deployed to theSystem Integration Test environment▬ All planned functional tests executed▬ Reporting – Quality Center and checklists
  •  Test process experiences Early test focus from all project participants Test focus throughout the whole development cycle All project participants responsible for test execution Continuous functional system test Continuous functional integration test Stable test environments for acceptance testing Bugs are found and corrected early Continuous quality verification Disadvantages?
  •  Thank you for your attention!