Scrum Team
Management
System (Scream)
Christopher Jolly
Alexander Kivaisi
Cliff Siyam
Outline
•
•
•
•
•
•
•
•
•
•
Brief description about Scrum
Problem Statement
Proposed Solution
Project Plan
Resources
Risks Management
Testing Strategy
Success Analysis
Ethical, Professional and Legal issues
Work Allocation
What is Scrum?
The Problem
Target Area
PROPOSED SOLUTION
Required features
Window Application(FrontEnd)
SCRUM PLANNING MEETING
SCRUM REVIEW MEETING
Product
Management
System
Sprint
Management
System
Graph
Generation
Searching
Sprint Stories
Cards
Generation
Report
Generation
Database (Back-End)
PROJECT PLAN
Implementation
•
•
•
•
Done the Scrum way
Sprints 1 week
Quick daily meetings
Aim to demo new functionality each
week to supervisor
Development platform and
resources
 Windows Environment
 Visual Studio 2010
 SQL Server 2008 R2
 Subversion over Apache
Risks
 Group member leaves
 Feature creep
 Under estimation of time per feature
Timeline
Milestones
Dates
Literature Survey
13 April-3 May
Project Proposal
4 May-12 May
Project Proposal Presentation
13 June-17 May
Revised Proposal
19 May-28 May
Inclusion of Project proposal and
Timeline on Project Web
First Prototype
1 June
Break
7 June-26 July
Background/Theory Chapter
26 July-30 July
Design Chapter
8 August-26 August
First Implementation,
Experiment, Performance Test +
Write-up
30 Aug-20 September
28 May-4 June
Timeline
Milestones
Dates
Sprint 1
26 August-2 September
Sprint 2
2 September-9 September
Sprint 3
9 September-16 September
Final Prototype, Experiment,
Performance Test + Write-up
Sprint 4
21 September- 29 September
Sprint 5
23 September-30 September
Implementation and Test
Complete. Coding complete
Outline of Complete Report
30 September-4 October
Final Complete Draft of Report
12 October-25 October
Final Project Report Handlin
26 October-1 November
16 September-23 September
5 October-11 October
Risks
Risk
ID
Risk
Probability
of Risk
Impact Consequences
of Risk
Mitigation
1
Group Member
leaves the group
Medium
Medium
Late
delivery/work
overload
Delegation of
tasks to other
members
2
Group Member
either felt sick or
does not complete
their section
Low
Medium
Delay delivery of
the system
4
Inadequate
communication
between project
team and
stakeholders
(Korbitec)
Medium
Medium
Unusable
deliverables
Eat well every
day!!!
Daily scrum
meeting will
help each other
to solve our
problems
Regular
meetings
should be set
fortnightly.
5
Certain sprint
stories might be
too big for one
person to handle
Medium
Medium
Might lead to late
delivery
Distribute to
other members
or solve others
problems
through daily
meetings
Testing
 Internal testing during each Sprint
− Unit tests
− Integration tests
 May be able to “dog food” the
product
 Live testing and feedback from
Korbitec
Success analysis
 Does it meet the requirements
specified?
 Is it simple and efficient?
 Is Korbitec satisfied with it?
Ethical, Legal and
Professional issues
 Using open-source code without
giving credit
 Using illegal software
 Reverse engineering code
 Taking talent from competition
 Intellectual property
Work Allocation
 Work closely inter-related
− Allocations may not be strictly
adhered to
 Chris
− Sprint story management and
Summary graph
 Alexander
− Sprint management and print output
 Cliff
− Project management and story
searching
Conclusion