1. SIS DEVOPS COMMUNICATION MODEL SIMULATOR
Amanda Crawford
Fall 2017
University of Pittsburgh

2. A Simple Small Agile Development Team
Product Owner
Responsible for the work item list (Epics)
Lead Developer/ Scrum Master
Facilitate team
Protect team from problems (Defects)
Developer
Creation and delivery of system (User story and Defects)

3. Communication Artifacts
We can use artifacts of the agile development process as a form of communication.
Epics
User Stories
Defects
Epic
User Story
User Story
User Story
Defect
Defect
Defect
Defect
Defect

4. Artifacts: Epic Epic Large user stories to describe a project feature
Contains high level requirements to build feature
Completed over multiple iterations
The full team works to complete a user story
Artifacts: Epic

5. Artifacts: Defects Defect Used to mark problems in a system
Defects are verified by user story requirements
A user story cannot be complete until all defects are cleared
Artifacts: Defects

6. Artifacts: User Story User Story Small and isolate feature component
Definition of done describes how a user story should be completed
Usually completed by one or two developers
Artifacts: User Story

7. Current Informal Communication Model
Product Owner
Development Lead
Developer
Current Informal Communication Model

8. Project Goal
We want to reduce the nee

9. Simulator
Simulates the communication model between development team members composed of human and system actors.
The simulator can be extended to a more robust team with additional roles
Reduces the need to communicate face to face between the product owner, developer, and dev lead

10. SIS DevOps Simulator Components
Development Team
Human Actors
Developer
Development Lead
Product Owner
Version Control Super Component
System Actor
Gist
Communication
Text Messaging
SIS DevOps Simulator Components

11. Web Based Platform
Tools:
Node JS
Angular 2
Git Gist API
Application

12. Human Actors Developer Development Lead Product Owner
The developer will be responsible for creating gists based on it’s related to a user story, defect, or epic.
Development Lead
The dev lead has the ability to subscribes to the developer’s user story and defect gist
The dev lead can create an epic gist
Product Owner
The product owner has the ability to subscribe to the developer’s defect gist and the development lead’s epic gist
This Photo by Unknown Author is licensed under CC BY-SA

13. Active Index Cells For Human Actors
Actions:
Submits User Story Gist
Submits Defect Gists
Actions:
Submits Epic Gist

14. Version Control System Actor: Gists
A Gist a way to share code and information among a group of individual. It is similar to repository as it can be forked.
Gists has a lightweight and easier protocol than Git repositories
There is a gist for epics, user stories, and defects.

15. Communication System Actor
A human actor can choose to receive information via text or .
The application only outputs the information to be sent but can be extended to using an or text messaging api.

16. SIS Communication Server System
Product Owner
Developer
Version Control Component
Communication Component
Lead Developer

17. Communication Patterns
Developer updates branch and communicates status via Gist
Development Lead and Product Owner subscribes to specific notification types:
Defects
User Story
Epic
Human to Actor Interactions
Git interacts with the notification system
Actor To Actor
Messaging Component sends the appropriate notification to the development lead and product owner
Actor to Human
Communication Patterns

18. Scenario Dev Lead Subscribes to Defect Updates via Email
Product Owner Defect Updates via Text
Developer Submits Defect Update
User Story Gist Updated
Notification Sends Text to Dev Lead and to Product Owner

19. Simulator

20. Conclusion & Discussion
The model allows dev team members the ability to expressly communicate their status via Gist features 01
The drawbacks are that the notification may not leverage the expressivity of Gist. 02
Conclusion & Discussion

21. Implement the Notification system with appropriate API’s
Develop a two way notification model that allows human actors to respond to updates
Future Work

22. References
Cois, C. A., Yankel, J., & Connell, A. (2014, October). Modern DevOps: Optimizing software development through effective system interactions. In Professional Communication Conference (IPCC), 2014 IEEE International (pp. 1-7). IEEE.
Roles On Agile Teams.