Managing risk and quality with Scrum

•

4 likes•1,995 views

The document defines Scrum and its processes like sprints, daily standups, and retrospectives. It discusses how Scrum manages risk through short iterations and frequent feedback rather than traditional upfront planning. Quality in Scrum is ensured by building working software incrementally in each sprint and getting stakeholder feedback, rather than only testing later. The author is Gunther Verheyen, a Scrum expert at Capgemini since 2010.

Gunther Verheyen 17 November 2010 Managing Risk & Quality with ScrumCapgemini Belgium

Table of Contents Definition of Scrum Managing Risk Managing Quality Author Managing Risk & Quality with Scrum, Gunther Verheyen, 17 November 2010 © 2010 Capgemini. All rights reserved. 2

1. Definition of Scrum “Scrum is about planning, building and demonstrating an increment of software, looking back at what happened, and repeatedly improving this process. Scrum calls for specific meetingsand rituals, and even a couple of artifacts, like burn-down charts.” (Ron Jeffries) Process: Sprint Planning Part 1: Product Owner explains Part 2: The Team discusses Sprint Daily Scrum 15’ to share information Apply ‘engineering standards’ Sprint Review / Demo Sprint Retrospective Managing Risk & Quality with Scrum, Gunther Verheyen, 17 November 2010 © 2010 Capgemini. All rights reserved. 4

2. Managing Risk Traditional Methods: 6 © 2010 Capgemini. All rights reserved. Managing Risk & Quality with Scrum, Gunther Verheyen, 17 November 2010

2. Managing Risk 7 © 2010 Capgemini. All rights reserved. Agile / Scrum: Managing Risk & Quality with Scrum, Gunther Verheyen, 17 November 2010

3. Managing Quality Working Software Traditional methods 9 © 2010 Capgemini. All rights reserved. Managing Risk & Quality with Scrum, Gunther Verheyen, 17 November 2010

3. Managing Quality Agile / Scrum Product Owner Build & demonstrate Stakeholder feedback Managing Risk & Quality with Scrum, Gunther Verheyen, 17 November 2010 © 2010 Capgemini. All rights reserved. 10

3. Managing Quality Technical Quality Daily Testing Short feedback loops Engineering standards Managing Risk & Quality with Scrum, Gunther Verheyen, 17 November 2010 © 2010 Capgemini. All rights reserved. 11

4. Author Gunther Verheyen(gunther.verheyen@capgemini.com) eXtreme Programming and Scrum since 2003 (CSM in 2004) Designed the ScrumPlus framework for fixed price projects Capgemini since March 2010 Board member for Capgemini of the Agile Consortium Belgium Community Leader for Agile/Scrum community in Belgium PSM I and II in 2010 (Scrum.org with Ken Schwaber) Contributor to Capgemini Technology Blog Twitter @Ullizee http://ullizee.wordpress.com 13 © 2010 Capgemini. All rights reserved. Managing Risk & Quality with Scrum, Gunther Verheyen, 17 November 2010

You can’t throw a party, if the front door is blocked. More than 60% of users sign up for a service, bounce during onboarding, and never return. If your company depends on developers, then how they get started, use, and contribute to your communities, libraries, tools and APIs should be more than just painless. Your onboarding design should be elegant. In this Heavybit Speaker Series presentation, GitHub Developer Advocate Brian Douglas will discuss: Best practices in designing a stellar first user experience; Tools, content and tactics to maintain user momentum; and, Examples of the breadcrumbs and carrots that communities like GitHub, Netlify, Stripe and Graphcool use to help developers succeed

Managing quality and risk in a prince2 aligned projectsidlko

Summer of Tech 2015: Scrum masterclass

aboobier

AgileCamp Silicon Valley 2015: Why Scrum Teams Should Care About Kanban

Hyperdrive Agile Leadership (powered by Bratton & Company)

[Thao Vo] Deadly Traps of Automation Testing

Ho Chi Minh City Software Testing Club

This training will provide a deep dive into Microsoft Team Foundation Server (TFS) for agile projects from setting up TFS through the end of the first sprint. This is a hands on training, attendees will actively engaged in a sample project using TFS in the cloud. Presenters will include senior Aspenware architects and project managers as well as Steve Lange, Developer Technology Specialist at Microsoft. This training is appropriate for developers, project managers and business analysts. A basic understanding of scrum and agile development is required. Part 2 Agenda *Brief review of Part I *Reporting and tracking features of TFS. *Setup Continuous Integration and discuss value *Setup an auto deployment to Azure *Testing features of TFS and how auto deployments aid that process *End of Sprint Demo *End of Sprint Retrospective *Use TFS to review the tasks and determine velocity on this Sprint *How to plan subsequent sprints

[Mush Honda] Metrics & Reports from Test Teams (QA)

Ho Chi Minh City Software Testing Club

As a part of testing management in a project, test leads are often requested to provide reports and measurements of progress being made by their team. Most of them limit their reports to templates found on the Internet or by simply providing number crunching metrics requested by the project stakeholders. The intent of this presentation is to highlight key goals and reasons and for collecting and reporting information from a tester’s perspective. Attend this presentation to understand the purpose of metrics and how to establish test-centric metrics and to learn a typical metric lifecycle that will enable to you provide insightful progress of your activities in the right context of the project.

Scrum Project Management

Aldo Santoso

A Testers Guide To Collaborating With Product Owners

TEST Huddle

In Scrum the Product Owner is relatively starkly defined. They are the owner of the Product Backlog and represent the “customer”. In many organizations, they “go it alone”, trying their best to represent business needs for their teams. What’s often missing in this approach is a wonderful collaborative connection between the teams’ testers and the Product Owner. A connection where testers help to define and refine requirements, broaden the testing landscape and align it to customer needs, provide a collaborate conduit between the customer and the team, assure that the team is building the “right thing”, and helping to demonstrate complete features . This relationship is not only central to the team, but facilitates transparency and helps gain feedback from the entire organization. Join seasoned agile coach Bob Galen as he shares stories and techniques for doing just this. You will return to your agile teams with new ideas and techniques for helping your Product Owner and team deliver better received and higher value products; not just by “testing”, but by “fostering collaboration”.

Hospital quality management

Mohammed Yaser Hussain

The methodology of patient satisfaction surveys ⇒ There has been a shift in thinking about the role of the consumer as patient. It is more likely now that researchers want to know what consumers think; that they accept that what the patient tells them is an accurate reflection of what happened; and that this information can be used to improve the quality of care. ⇒ Coinciding with this shift, and related to it, is a serious questioning of the conception of satisfaction as a unitary concept whose causal variables can be measured. ⇒ Researchers now are more in favour of using several research methods, drawn from qualitative and quantitative research, to inform their survey instruments, and gather data. ⇒ The methodological complexities of patient satisfaction research are considerable and should not be downplayed. ⇒ Certain groups of people, whose social position or state of health may make them vulnerable to poorer quality care, are extremely difficult to reach via the conventional questionnaire. The use of patient satisfaction surveys ⇒ There is a need to develop greater expertise, greater support to those doing patient satisfaction work, more coordination at hospital level, greater commitment to acting on the results, and involvement of consumers at all stages of patient satisfaction work, including acting on the results. ⇒ Much patient satisfaction work treats consumers passively, that is, as providers of information, which administrators and providers may or may not do something with. ⇒ There is a need to develop appropriate infrastructure for undertaking patient satisfaction work, to develop the level of expertise, and to consider the role which independent organisations based on a consumer perspective might play in undertaking consumer appraisal activities and research in joint activities with hospitals and purchasers. ii ⇒ There are questions about whose views are sought in patient satisfaction surveys and there is a challenge to incorporate the view of those consumers who are most in need of good quality services, who are very ill, whose views are regarded as being difficult to obtain and those who are often at risk in the quality of their care. Benchmarking ⇒ The purpose for undertaking consumer feedback activity needs to be articulated and owned by hospitals as part of their overall organisational strategy. ⇒ The processes that produce patient satisfaction are more important to understand

Team foundation server als perfecte tool voor scrum (TechDays 2013)

Delta-N

Scrum is een proces om complexe software te kunnen maken. Om Scrum te doen zijn in principe geen tools nodig. Echter, het maakt het wel een stuk makkelijker als dit wel wordt gedaan. Visual Studio ALM 2012 biedt vele mogelijkheden voor het ondersteunen van het Scrum proces. In deze sessie zullen de verschillende fases (Release Planning, Sprint Planning, Sprint, Review, Retrospective) van Scrum worden doorlopen en wordt stilgestaan bij de vraag hoe Team Foundation Server hierbij kan ondersteunen. Deze sessie gaat niet in op de details van het Scrum proces.

What I wish I knew on my first Scrum sprints :: Conferencia Agile Spain 2015

Pedro Gustavo Torres

Introduction to Back End Automation Testing - Nguyen Vu Hoang, Hoang Phi

Ho Chi Minh City Software Testing Club

Back-end testing is an unfamiliar testing area to many testers, especially when the Back-end adopts web services technologies and has gigabytes of data need to be verified. The presentation will outlines numbers of testing activities that need to be done to deal with challenges. Services/Domain Testing Introduction: We have been providing automation test service for Back-end system which has web services, web application technologies and meta-data processing. The domain we has worked on is about Communication Media and Entertainment. Challenges: Complex business logic inside layer of data storage and processing to provide services. Different platforms under test. Defragmented testing result so it is difficult to make decision. Must align testing with development life cycle. Solutions: Apply automation testing to Continuous Integration. Design automation test framework to deal with Shell, Web Service, Web Application, gigabytes of XML Data on Windows and Linux. Select proper technology stack to centralize the testing result from both manual and automation teams. Jenkins is continuous integration and continuous delivery application, as start point, run its job to build source code from development team. When unit testing for source code is passed, automated system test written by LISA is launched as flow controller for automation test framework. The LISA’s core functionalities are to verify middleware layer, web services based on SOAP/RESTful and database. Extending LISA’ capabilities are also applied in practice to test different technologies under test such as web application by integrating with Selenium, Shell Script by JCraft and processing big data file by Xstream/JAXB.

Managing Qualityknksmart

Operations - Managing Qualitytutor2u

High Quality Software Development with Agile and Scrum

Lemi Orhan Ergin

Agile Testing Days 2015 - PIMP MY SCRUM – DOCUMENTATION FUN FOR AGILE TEAMS

Anis Ben Hamidene

Scrum with it’s few artefacts, roles and meetings is already fun. The documentation task for most developers and testers is still just boring. Because of this, documentation seldom serves as it’s intended purpose. It is rarely complete, up to date or clear enough to avoid misunderstandings. So you don’t trust documentation, do you? If you can get hold of the people who you know what the software is doing, you ask them instead. Nowadays Behaviour driven development (BDD) makes documentation not only for developers more fun, but also serves as a trust building documentation. Further, it helps to clarify the intent of the story or requirement before implementation starts and validates it continuously after it is released. Sounds impossible? In this track we make the BDD concept of a Living Documentation a reality. We share with you our experiences about the methods and tools which support the notion of BDD and provide practical guidance about which tools are best suited for your context. We will be also happy to share with you the premiere of our open source suite testIT LivingDoc, a BDD solution for Atlassian Confluence and the successor of the popular but almost dead GreenPepper.

ScrumDay Germany - The Future Present of Scrum

Managing risk and quality with Scrum

Recommended

Recommended

More Related Content

Viewers also liked

Viewers also liked (16)

Similar to Managing risk and quality with Scrum

Similar to Managing risk and quality with Scrum (20)

More from Gunther Verheyen

More from Gunther Verheyen (20)

Recently uploaded

Recently uploaded (20)

Managing risk and quality with Scrum