Amanda Crawford Fall 2017 University of Pittsburgh A Simple Small Agile Development Team Product Owner Responsible for the work item list Epics Lead Developer Scrum Master Facilitate team ID: 933624
Download Presentation The PPT/PDF document "SIS DEVOPS COMMUNICATION MODEL SIMULATOR" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
Slide1
SIS DEVOPS COMMUNICATION MODEL SIMULATOR
Amanda Crawford
Fall 2017
University of Pittsburgh
Slide2A Simple Small Agile Development TeamProduct OwnerResponsible for the work item list (Epics)Lead Developer/ Scrum Master Facilitate teamProtect team from problems (Defects)DeveloperCreation and delivery of system (User story and Defects)
Slide3Communication ArtifactsWe can use artifacts of the agile development process as a form of communication.EpicsUser StoriesDefects
EpicUser Story
User StoryUser Story
DefectDefect
DefectDefectDefect
Slide4Artifacts: 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
Slide5Artifacts: 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
Slide6Artifacts: 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
Slide7Current Informal Communication Model
Developer
Development Lead
Product Owner
Slide8Project GoalWe want to reduce the nee
Slide9SimulatorSimulates 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 rolesReduces the need to communicate face to face between the product owner, developer, and dev lead
Slide10SIS DevOps Simulator Components
Slide11Application
Slide12Human ActorsDeveloperThe developer will be responsible for creating gists based on it’s related to a user story, defect, or epic.Development LeadThe dev lead has the ability to subscribes to the developer’s user story and defect gistThe dev lead can create an epic gist Product OwnerThe 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
Slide13Active Index Cells For Human Actors
Actions:
Submits Epic Gist
Actions:
Submits User Story Gist Submits Defect Gists
Slide14Version 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 repositoriesThere is a gist for epics, user stories, and defects.
Slide15Communication System Actor
A human actor can choose to receive information via text or email.
The application only outputs the information to be sent but can be extended to using an email or text messaging api.
Slide16SIS Communication Server System
Communication Component
Version Control Component
Developer
Product Owner
Lead Developer
Slide17Communication Patterns
Slide18Scenario
Slide19Simulator
Slide20Conclusion & Discussion
Slide21Future Work
Slide22ReferencesCois, 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.http://www.ambysoft.com/essays/agileRoles.html