slide1 n.
Skip this Video
Loading SlideShow in 5 Seconds..
CSE G674/2009 Project Project Management Section Presented by: Amir Aref Adib PowerPoint Presentation
Download Presentation
CSE G674/2009 Project Project Management Section Presented by: Amir Aref Adib

CSE G674/2009 Project Project Management Section Presented by: Amir Aref Adib

75 Vues Download Presentation
Télécharger la présentation

CSE G674/2009 Project Project Management Section Presented by: Amir Aref Adib

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. CSE G674/2009 Project Project Management Section Presented by: Amir ArefAdib

  2. Main Goal for 2009 Project: The goal for this year’s project is to expand the code capability of SEP 2008 and adding more functionality, and focus on a different aspect of information about a software engineering project.

  3. The Challenges How we should start the project? Time limitation Different people different taste and idea How we can manage the project New topic and …..

  4. what should we do as a team to facilities these difficulties?

  5. Define Project Management frame work for our project Define time frame work Clear what we want and what we should do Divide whole project to small parts

  6. Eclipse Process Framework Project (EPF) The Eclipse Process Framework (EPF) aims at producing a customizable software process engineering framework, with exemplary process content and tools, supporting a broad variety of project types and development styles. EPF Goal By using EPF Composer you can create your own Software development process by structuring it in one specific way using a predefined schema.

  7. EPF

  8. Project Management After discussion with theclass, weall decided to apply Agile methodologies for this year’s project. We believe our project can adapt Agile/Scrum methodologies. In result, we summarized the main concepts of Agile methodologies that we can apply in our project as a framework inEPF.

  9. Scrum Overview: Scrum is an experimental Agile project management framework used to deliver increments of high value to the customer iteratively. Scrum relies on self organizing, empowered teams to deliver the product increments. It also relies on a customer , or Product Owner, to provide a team with a list of desired features using business value as the priority mechanism.

  10. Daily Communication Weekly Scrum Meeting One week or two weeks Backlog tasks expanded by team Sprint Backlog Potentially Shippable Product Increment Product Backlog As prioritized by Product Owner

  11. General role for team Each team does not include any of the traditional software engineering roles such as programmer, designer, tester, or architect. Everyone on the project works together to complete the set of work they have collectively committed to complete within a sprint. Scrum teams develop a deep form of camaraderie and a feeling that "we're all in this together." Each member was responsible to complete all the assignments that were assigned to him/her in each sprint.

  12. Some of the principles behind the Agile Manifesto are: Customer satisfaction by rapid, continuous delivery Working software is delivered frequently Working software is the principal measure of progress Even late changes in requirements are welcomed Close, cooperation between all members Face-to-face conversation is the best Projects are built around motivated individuals, who should be trusted Simplicity Self-organizing teams Regular adaptation to changing circumstances

  13. No Change! • We are already running late. • I need to meet my date. • We worked hard to prevent change at the start. Cost of change Promised date

  14. The following terminology is used in Scrum: Roles Product Owner /PM: The person responsible for maintaining the Product Backlog by representing the interests of the customer. ScrumMaster/ Leader : The person responsible for the Scrum process, making sure it is used correctly and maximizes its benefits. Team : A cross-functional group of people responsible for managing itself to develop the product. Scrum Team Product Owner, ScrumMaster and Team

  15. Artifacts • Sprint burn down chart weekly progress for a Sprint over the sprint's length. • Product backlog A prioritized list of high level requirements. • Sprint backlog A list of tasks to be completed during the sprint.

  16. Find out any possible extensions and improvements Research On Previous project Research on new topic Working on development Work on UML Working on Requirements and documentation Integration

  17. Project Schedule 2/25: By this date all groups should have clear idea (extensions) and interfaces with other groups. they should working on their extensions and interfaces. At least 50% of their works should be finished at this point. 3/30: All design (extensions)should be complete by this point and all tools should successfully be integrated . (Our goal is to be done with everything by this date) 3/31: Final testing and finalize documentation begin 4/13: End of Class! Final presentation, all deliverables. Say goodbye, have fun for summer break:)

  18. If the decision were solely up to you, would you continue using Scrum?

  19. Red Yellow Green Blue Red Blue Yellow Green Blue

  20. Yahoo survey 80% Yes 94% Yes India US 88% Yes 82% Yes Overall Europe Source,Yahoo.ppt

  21. Advise to Next Group: • Extend EPF and link it with your project. • Review our final Specification • Review Our task board, It will provide list of tasks and estimation on each task (time frame work) • Review sprint backlog of each team.

  22. THANK YOU ! You can find out more information at: Book “Agile Software Development with SCRUM” by Ken Schwaber, Mike Beedle Book “Agile Project Management with SCRUM” by Ken Schwaber - Ken Schwaber’s own site Scrum for Managers Source :