The document discusses defining "Done" for Scrum teams working in cloud environments like AWS and IBM Bluemix. It proposes a 10-step Definition of Done checklist within GitLab's single interface that covers the full feature life cycle from idea to completion. This includes steps like writing code, testing, code reviews, monitoring, and updating documentation. The checklist is intended to provide transparency for Scrum artifacts like product and sprint backlogs being developed in cloud infrastructure as a service environments.

1. Scrum’s Definition
of Done
in the
Cloud

2. Scrum’s Definition
of Done
Super Important: “Definition of done is crucial to a highly functioning
Scrum team.” -www.scrumalliance.org 1st sent.
Scrum Guide: “When a PBI or an increment is “done,” everyone must
understand what “Done” means.” (Scrum Guide, sent. 1, paragraph 1,
p.16) “The same def. guides the Dev. Team in knowing how many
PBI’s it can select during Spring Planning.” (Scrum Guide, sent. 1,
paragraph 2, p.16)
Checklist to provide “artifact” (p.backlog, s.backlog, increment)
transparency. “Scrum relies on transparency.”

3. Cloud is a network of servers
doing stuff, functions like:
storage, processing requests,
running and monitoring apps.
What else?

4. Infrastructure as a Service
“Virtualization of someone else’s hardware managed via an API,
allows for programmatic access to compute, storage, and network
resources and configuration.
Request a new virtual machine when you need it, terminate it
when you’re done with it, and only pay for what you use.
Treat data center resources like a utility.”

5. DevOPS
Just got a whole lot easier.

6. Background
Business need- deliver value fast, high quality, reliable, easy to
change, adapt, scale- agile. Transitioning into an enterprise class
DevOps environment- incorporating a shared understanding
between business and development we needed a definition of
done to track feature releases throughout the entire SDLC.
CMYK
(štiribarvni tisk)
B
PANTONE UNCOATED
(tribarvni tisk)
ZELENA: PMS 381 U
MODRA: PMS 313 U
RNA: PMS Black

7. Background
"Definition of Done," a foundational Scrum document,
into the cloud. Currently, to my knowledge, there's no
known example of it for cloud, Infrastructure as a
Service (IaaS) environments like Gitlab, AWS, and
IBM's Blue Mix.
CMYK
(štiribarvni tisk)
B
PANTONE UNCOATED
(tribarvni tisk)
ZELENA: PMS 381 U
MODRA: PMS 313 U
RNA: PMS Black

8. DigiPops.TV
Definition of Done Checklist
10 step feature life-cycle (FLC) from idea to done
within GitLab’s single UI framework.
CMYK
(štiribarvni tisk)
B
PANTONE UNCOATED
(tribarvni tisk)
ZELENA: PMS 381 U
MODRA: PMS 313 U
RNA: PMS Black

9. Idea & Plan
Create Issue
Write Code Components
Commit
CI: Create/Update Unit Tests
Conduct Code Review
Create/ Update Automated Acceptance Test
Perform Code Coverage Test
Run Performance Tests
Update User Guide
Update Online Context Help
Monitoring
Feedback

10. Konstantin Rubchinsky
DigiPops, Agile Lead
konstantin@digipops.tv
Amara Nwaigwe
Dir. of Product Marketing
amara@gitlab.com
Richard Baum
Success Engineer
reb@gitlab.com

11. IAC
“Infrastructure as Code (IaC) is the process of managing and provisioning computing infrastructure
(processes, bare-metal servers, virtual servers, etc.) and their configuration through machine-processable
definition files, rather than physical hardware configuration or the use of interactive configuration tools.
Infrastructure as Code approaches have become increasingly widespread with the adoption of cloud
computing, which is sometimes marketed as “infrastructure as a service” (IaaS). IaC supports IaaS.
IaC grew as a response to the difficulty posed from two pieces of disruptive technology – utility computing
and second-generation web frameworks. This brought about widespread scaling problems for many
enterprises that were previously only witnessed by huge companies.[2] In 2006 specifically, new challenges
were brought to the forefront that shook the technology industry; the launch of Amazon Web Services’
Elastic Compute Cloud and the 1.0 version of Ruby on Rails just months before.[3] With new tools
emerging to handle this ever growing field, the idea of Infrastructure as Code was born. The thought of
modeling infrastructure with code, and then having the ability to design, implement, and deploy
applications infrastructure with known software best practices appealed to software developers and IT
infrastructure administrators. The ability to treat it like code and use the same tools as any other software
project would allow developers to rapidly deploy applications.”