Hello. Using the Epics & User Stories material from the 4/16 lecture (AgileScrum.pptx in theI attachment below), please answer the followin
Hello. Using the Epics & User Stories material from the 4/16 lecture (AgileScrum.pptx in theI attachment below), please answer the following:
What type of role and employer do you hope to work in after you complete your collegiate studies (eg your position & the entity)?
What products or services are provided by this employer?
Who are the key User Groups of the entity (eg if the entity was CSUF, three key user groups or user types are Students, Faculty, & Administration)?
For each key user group, please provide a User Story in the following format:
As a [user type], I want to [achieve some outcome] so that [some purpose is attained]
An example of a user story for my role is: As an Instructor of CPSC 313, I want to teach students about the computer’s impacts on society so that they have additional understanding of the world around them.
I need 2 pages
CPSC 313 58-59
Spring 2022
Development Models &
Agile Methodologies
Randall Lee
Generic Process Model
Communication – with the Customer and other key stakeholders
Planning – Key Tasks, Risks, Resources, Work Products, & Schedule in Project Plan
Modeling – Unified & Class Modeling
Construction – Coding & Testing
Deployment – Implementation
The Waterfall Model
Linear process model
Framework of Activities, Actions, & Tasks occur in a sequential fashion
OK to use when requirements are well-defined and reasonably stable
Evolutionary Process Models
Prototyping, an Iterative Model that is:
Used to develop a working concept when requirements are not well-known nor well-defined.
Requirements become more refined with each prototype and customer feedback
The Spiral Process Model
The Spiral Process Model combines the iterative approach of prototyping with the sequential nature of the Waterfall process. This evolutionary process can reduce risks and be used throughout a software program’s lifecycle. However, number and speed of iterations may be unknown.
The Unified Process
Iterative, Sequential, but not necessarily Evolutionary
Inception Phase – spans Communication & Planning stages
Elaboration Phase – spans Planning & Modeling stages
Construction Phase – similar to the Generic Model
Transition Phase – spans Construction & Deployment
Production Phase – the released software increment
Principles Behind the Agile Manifesto (1-6)
We follow these principles:
Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.
Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
Business people and developers must work together daily throughout the project.
Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
Principles Behind the Agile Manifesto (7-12)
Working software is the primary measure of progress.
Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
Continuous attention to technical excellence and good design enhances agility.
Simplicity – the art of maximizing the amount of work not done – is essential.
The best architectures, requirements, and designs emerge from self-organizing teams.
At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
Extreme Programming (XP) Process Model
Key Features of XP:
User Stories, Values, & Costs – priorities & weeks of time
Class-Responsibility-Collaborator (CRC) Cards
Prototyping
Pair Programming – two developers at one workstation
Unit Testing at the functional, class, or procedural levels
Acceptance Testing of the acceptance criteria
Release of Software Increment
Scrum Framework as a Process Model
To form the Product Backlog, User Stories are created, story-pointed, and prioritized before the first sprint. The duration of every sprint is time-boxed to a fixed period of time. During Sprint Planning, the Scrum Team decides what Product Backlog items they will develop during the Sprint. This becomes the Sprint Backlog. Each work morning, a Daily Scrum is held to determine what each team member worked on previously, what obstacles they are encountering, and what they will be working on today. Towards the end of each Sprint, a Sprint Review is held with key stakeholders. The team concludes with a Sprint Retrospective to prepare for the next Sprint.
User Stories, Story Points, & Velocity
Each User Story should be in the format “As a [user], I want to [achieve some outcome] for [some purpose]” The following examples are more like Epics, which User Stories are derived from.
As an Instructor of CPSC 313, I want to teach students about the computer’s impacts on society so that they have additional understanding of the world around them.
As a Student of CPSC 313, I want to learn about the computer’s impacts on society so that I understand how it influences the world around me.
Each User Story should have a Priority Rating {High, Medium, Low} and a Story Point Rating {1,2,3,5,8,13}
Velocity, Central Tendency & Dispersion II
What conclusions do you draw from the following?
Six Sigma & the Normal Distribution
1) Calculate Variance (Var) for Team Windows by first finding the Mean, or Average. The Mean is the (Sum of all outcomes of 300) / (No. of outcomes of 6) = 50
2) Then, Find & Sum all 6 of the Squared Deviations = ((each outcome – Mean) ^ 2)
((49-50)^2) + ((50-50)^2) + ((50-50)^2) + ((50-50)^2) + ((50-50)^2) + ((51-50)^2) =
1 + 0 + 0 + 0 + 0 + 1 = 2
3) For Variance, Divide the (Sum of the Squared Deviations of 2) / (No. of Outcomes – 1, or 5) = .40
4) For Standard Deviation (SD), Calculate the Square Root of the Variance = (.40)^(.5) = .63
Confidence Intervals for Team Windows
If Team Windows continues to produce with a Mean of 50 & a SD of .63, we should expect the following:
Around 68.3% of the outcomes should fall between +1SD around the Mean (Low = Mean-(1SD) = 50 – .63 = 49.37; (High = Mean+(1SD) = 50 + .63 = 50.63
Around 95.5% of the outcomes should fall between +2SD around the Mean (Low = Mean-(2SD) = 50-(2*.63) = 48.74; (High = Mean+(2SD) = 50+(2*.63) = 51.26
Around 99.7% of the outcomes should fall between +3SD around the Mean (Low = Mean-(3SD) = 50-(3*.63) = 48.11; (High = Mean+(3SD) = 50+(3*.63) = 51.89
16
References
Pressman, R & Maxim, B (2015). Software Engineering: A Practitioner’s Approach, 8th ed. McGraw Hill Education: New York, NY.
Schwaber, K & Sutherland, J (2020, Nov). The Scrum Guide: the Definitive Guide to Scrum, the Rules of the Game. Scrum.org
Beck, K, Cunningham, W, Thomas, D, Sutherland, J, Schwaber, K, et al (2001). Principles Behind the Agile Manifesto. https:// agilemanifesto.org/principles.html
Selleo (2021, Mar). Agile Values and Principles – Do They Still Matter? https:// selleo.com/blog/agile-values-and-principles-do-they-still-matter
Hayes, A (2021, Oct). Confidence Intervals. Investopedia. https:// www.investopedia.com/terms/c/confidenceinterval.asp
Sheet1
| Sprint | 1 | 2 | 3 | 4 | 5 | 6 | Mean | Median | Mode | Var | SD |
| Team Windows | 49 | 50 | 50 | 50 | 50 | 51 | 50 | 50 | 50 | 0.40 | 0.63 |
| Team Linux | 48 | 50 | 50 | 50 | 50 | 52 | 50 | 50 | 50 | 1.60 | 1.26 |
| Team Android | 48 | 49 | 50 | 50 | 51 | 52 | 50 | 50 | 50 | 2.00 | 1.41 |
| Team iOS | 45 | 47 | 50 | 50 | 53 | 55 | 50 | 50 | 50 | 13.60 | 3.69 |
| Team AgileLean | 99 | 100 | 100 | 100 | 100 | 101 | 100 | 100 | 100 | 0.40 | 0.63 |
Sheet2
Sheet3
Collepals.com Plagiarism Free Papers
Are you looking for custom essay writing service or even dissertation writing services? Just request for our write my paper service, and we'll match you with the best essay writer in your subject! With an exceptional team of professional academic experts in a wide range of subjects, we can guarantee you an unrivaled quality of custom-written papers.
Get ZERO PLAGIARISM, HUMAN WRITTEN ESSAYS
Why Hire Collepals.com writers to do your paper?
Quality- We are experienced and have access to ample research materials.
We write plagiarism Free Content
Confidential- We never share or sell your personal information to third parties.
Support-Chat with us today! We are always waiting to answer all your questions.
