1 / 15

Software Engineering Projects 2IP35

Software Engineering Projects 2IP35. Autumn 2013. Today: kick-off. General information about the projects Presentation by the customers Groups subscribe to cases Coupling of groups to cases. General information. A real project A real customer A team consists of 8-10 students

Download Presentation

Software Engineering Projects 2IP35

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. Software Engineering Projects2IP35 Autumn 2013

  2. Today: kick-off • General information about the projects • Presentation by the customers • Groups subscribe to cases • Coupling of groups to cases

  3. General information • A real project • A real customer • A team consists of 8-10 students • Separate project and quality manager (students 2IP45) • Each team has an advisor (staff member) • Timing • Available time: 12 Ects  336 hours per person • Start: September 2, 2013 • Deadline: October 25, 2013

  4. Organization

  5. Documentation • According to the ESA standard • Project documents: • SPMP: Software Project Management Plan • SVVP: Software Verification and Validation Plan • SCMP: Software Configuration Management Plan • SQAP: Software Quality Assurance Plan • Product documents: • URD: User Requirements Document • SRD: Software Requirements Document • ADD: Architectural Design Document • DDD: Detailed Design Document • SUM: Software User Manual • STD: Software Transfer Document • Project includes “provisional” acceptance, no maintenance • All product documents delivered to customer • All documents delivered to senior management

  6. Project planning

  7. Sprint planning

  8. Scrum

  9. Some project procedures • First requirements, than agile coding (scrum) • URD contains backlog list. • Some prototyping in early phase. • Tackle technical risks by advanced research • Formal review procedure of documents • Pre-check by advisor • Attention points from checklists • Customer involved in: • URD, SRD, SUM, and Acceptance Test review • Results and review metrics reported to senior management • Signature needed of customer and/or advisor • Reporting to management • Time metrics (weekly) • Progress (weekly) • Review metrics

  10. Management roles and tasks • Project manager / scrum master • Planning: chairs planning sessions, stand up meetings, demos and retrospectives • Organizes scrum board, keeps back log up to date • Takes care that management documents are written • Reports progress to senior management: • Weekly progress sessions • Weekly e-mail metrics (time tracking) • Quality engineer / manager • Checks quality of documents • Takes care that reviews are held • Takes care that a proper testing environment is set up by the group • Enforces “continuous testing” approach • Organizes peer reviews

  11. Devils triangle We have • Fixed budget • Fixed time

  12. Group work • Write project plans • Work according to plans • Registration of hours spent • Divide work into work packages • Choose replacements for project manager, librarian and quality engineer • Write product documents • Advisor “helps” • One person responsible for customer contacts • Contacts with senior management via project manager • Facilities • Project rooms: MF 3.061, 3.104 • Network, (virtual) server

  13. Formal meetings • Weekly project meetings • Total team, circa 1 hour • Headed by project manager • Preferably also advisor present • In the scrum phase: replaced by sprint planning, demo, retrospective. • Weekly progress meetings • Project manager, quality engineer and senior management • 20 minutes for each group, Monday • Document reviews • General meetings • Intermediate presentation: September 30, 2013 • URD, (part of) SRD, prototype • End presentation: October 21, 2013 • Project overview, product demo

  14. Short term work • Define project name • Establish weekly meeting schedule • Contact between group and project manager • Contact advisor • Assign responsibilities • Write project plans • Look at examples from previous years (lead time decreased!) • Make inventory of available time (exams, holidays, …) • Start UR group (2-3 people) • Go to customer • Ask questions • Write iteratively versions of URD • Involve customer as much as possible • Set up development environment • Including configuration management • Perform research into technical questions • Read about scrum

  15. Customer presentations • Paul Jansen (Bradon) • Peter Vink (TNO-ESI)

More Related