sprint (1) deliverables capstone courses. what are sprint (1) deliverables ? 1.introductory parts...
Post on 27-Dec-2015
220 Views
Preview:
TRANSCRIPT
What are Sprint (1) Deliverables ?
1. Introductory Parts2. High level planning and scheduling (with risk
assessment) 3. High level features diagram4. High level architectural design diagram (UML
class diagram) 5. First initial prototype (non-functional mockup)
(Please read instructions next slide)
Sprint (1) Instructions
- A PPT presentation should be used and posted by the due date on the main discussion board on Webct
- Introduce your team in the first slide - All team members should participate - No report is required for Sprint (1) - Invite your sponsor to your class presentation (you will get
extra credits if they attended) - Creativity and outstanding efforts will be always rewarded - No dress code is required in the first sprint (professionally
dressed teams get extra credit for Sprint (2) [Midterm]. This will be a requirement though for both final presentation and the showcase)
1- Introductory Parts• Background (what is wrong with the AS-IS system) -required• Problem Statement (what should be done TO-BE system)-required• Market Research-optional
Previous work is well defined and analyzed (Literature Review) with proper citation
• Methodology Selection-optional Methodology is well defined and evaluated quantitatively ( evaluation matrix) with Pre/Post Analysis
• Glossary-required• Project Organization- This is not an item but a required criterion
The proposal is well organized with numbering, title page , references and appendix.
2-High Level Planning/Scheduling
• WBS required
• Gannt/Pert Charts (with 5 sprints) required
• Risk Assessment required Optional deliverables (bonus points):
1- Cost Estimation (if applicable)
2- Cost-Benefit Analysis (if applicable)
WBS• Work Breakdown structure• Breakdown phases into sub phases• Breakdown sub phases into tasks• Breakdown tasks into subtasks• Estimate durations (starting and ending times)• Determine predecessors • Allocate resources
Top Down Task Identification
PhasesPhases with
high level steps
Work Plan Deliverables Estimated Actual Assignedhours hours To
****
Risk management requirements
• Risk impact: the loss associated with the event
• Risk probability: the likelihood that the event will occur
• Risk control: the degree to which we can change the outcome
Risk exposure = (risk probability) x (risk impact)
Three strategies for risk reduction
• avoiding the risk: change requirements for performance or functionality
• transferring the risk: transfer to other system, or buy insurance
• assuming the risk: accept and control it
risk leverage = difference in risk exposure divided by cost of reducing the risk
3- High level features diagram
• List Features required
• Group Features required
• Map Features required
• Schedule/Track Features optional
Dec 2001
Completion Percentage:
Completion Status:
Completed
Targeted Completion Month
Example:Feature Set:
Making Product Assess’ts – Work in Progress
CP-1 is the Chief Programmer’s initials
(14) there are fourteen features that make up this feature set
75% Feature Set is 75% complete
Target is to complete in Dec 2001
Overall Status:
MY
Progress bar
Work in progress
Attention (ie, Behind)
Completed
MakingProduct
Assessments(14)
75%Not yet started
CP-1
FDD UML Extensions
Product Sale Management (PS)
InvoicingSales
(33)
Dec 2001
CP-1
Setting upProduct
Agreements(13)
Dec 2001
SellingProducts
(22)
Nov 2001
CP-1
ShippingProducts
(19)
Dec 2001
CP-1
10%
DeliveringProducts
(10)
Dec 2001
CP-3
30%
MakingProduct
Assessments(14)
Dec 2001
75%99% 3%
Customer A/C Mgmt (CA)
EvaluatingAccount
Applications(23)
Oct 2001
95%
LoggingAccount
Transactions(30)
Nov 2001
82%
OpeningNew
Accounts(11)
Oct 2001
100%
Inventory Mgmt (IM)
EstablishingStorage Units
(26)
Nov 2001
100%
MovingContent
(19)
Nov 2001
82%
CP-3
AcceptingMovementRequests
(18)
Nov 2001
97%
CP-3
KEY: Work In Progress Attention Completed Progress Bar Not Started
CP-2 CP-1
CP-2 CP-2 CP-2 CP-3
FDD Sample Features Diagram
4-High level architectural design
diagram (UML class diagram)
• Identify Classes, attributes and methods
• Identify relationships (associations, aggregations an inheritance)
• Determine multiplicities (or cardinalities)
• Draw a UML class diagram to map all these components
Class Diagram Concepts
• A static model that shows the classes and relationships among classes that remain constant in the system over time
• Resembles the ERD, but depicts classes which include both behaviors and states, while entities in the ERD include only attributes
• Scope not system wide, but pertaining to a single use-case
Steps in Creating a Class Diagram
1. Identify classes
2. Identify attributes and operations
3. Draw relationships between classes
top related