1 / 19

Enhancing Scrum Team Management with Scream: A Comprehensive Project Overview

This document outlines the Scrum Team Management System (Scream), developed to streamline project management using Scrum methodology. It includes a detailed problem statement addressing current inefficiencies, proposed solutions featuring both front-end and back-end development components, and a project plan outlining key resources, risks, and allocation strategies. The system incorporates essential Scrum rituals like planning and review meetings, enables effective sprint management, and features meticulous risk management and testing strategies. Key implications related to ethics and legal considerations are also discussed.

armand
Télécharger la présentation

Enhancing Scrum Team Management with Scream: A Comprehensive Project Overview

An Image/Link below is provided (as is) to download presentation 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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Scrum Team Management System (Scream) Christopher Jolly Alexander Kivaisi Cliff Siyam

  2. 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

  3. What is Scrum?

  4. The Problem

  5. Target Area

  6. Proposed Solution

  7. 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)

  8. Project plan

  9. Implementation • Done the Scrum way • Sprints 1 week • Quick daily meetings • Aim to demo new functionality each week to supervisor

  10. Development platform and resources • Windows Environment • Visual Studio 2010 • SQL Server 2008 R2 • Subversion over Apache

  11. Risks • Group member leaves • Feature creep • Under estimation of time per feature

  12. Timeline

  13. Timeline

  14. Risks

  15. Testing • Internal testing during each Sprint • Unit tests • Integration tests • May be able to “dog food” the product • Live testing and feedback from Korbitec

  16. Success analysis • Does it meet the requirements specified? • Is it simple and efficient? • Is Korbitec satisfied with it?

  17. Ethical, Legal and Professional issues • Using open-source code without giving credit • Using illegal software • Reverse engineering code • Taking talent from competition • Intellectual property

  18. 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

  19. Conclusion

More Related