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
Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
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
Required features Window Application(Front-End) SCRUM PLANNING MEETING SCRUM REVIEW MEETING Product Management System Sprint Management System Graph Generation Searching Sprint Stories Cards Generation Report Generation Database (Back-End)
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
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