1Lou Somers Software Engineering Projects 2IP35 Autumn 2014

Slides:



Advertisements
Similar presentations
Beta Testing: The Contractor’s Perspective Trns·port User Group Meeting October 2005.
Advertisements

Steve Collins Richland County IT Manager Agile.  Have Fun  Learn About Agile  Tell Some Stories.
Agile at ON.Lab Bill Snow VP of Engineering. What is waterfall? RequirementsDesignDevelopTest Or Requirements Design Develop Test Time.
<<replace with Customer Logo>>
Agile Project Management with Scrum
SCRUM John Drew. SCRUM - overview Scrum is a project management discipline that has evolved since the early 1990s to deliver software that meets business.
Scrum. An evolutionary/iterative/incremental/agile software process The main roles in Scrum are: – Scrum team: Team of software developers – Scrum master.
Implementation I - demo. Schedule * Project status -achieving the goals of the iteration -project metrics * Used work practices * Work results -presenting.
GAI Proprietary Information
Stepan Potiyenko ISS Sr.SW Developer.
CSE 784 Software Studio Phil Pratt-Szeliga Fall 2010 Slides Derived From: Dr. Fawcett.
Creator: ACSession No: 19 Slide No: 1Reviewer: - CSE300Advanced Software EngineeringMarch 2007 ‘Agile Methods’ (part 2) CSE300 Advanced Software Engineering.
Difference between project and other assignments real customer before programming: negotiations with client to clarify requirements often changes.
Defining the Activities. Documents  Goal Statement defines why helps manage expectations  Statement of Work what gets delivered defines scope  Software.
The Product Owner prioritizes the requirements or features through feedback from the Stakeholders & interaction with the core team The Team.
PopMedNet Software Development Life Cycle Chayim Herzig-Marx Harvard Pilgrim Health Care Institute Daniel Dee Lincoln Peak Partners.
Trusted IT Group. The challenge: 40 active, concurrent IT projects  Unsatisfactory Project Delivery.
Distributed Software Development Transport4You1 Project Plan Gaurav Kushwaha & Dajan Zvekic.
Software Engineering- Scrum 徐 瑋 Alen 林芳瑜 Flora 1.
Page 1 MODEL TEST in the small GENERALIZE PROGRAM PROCESS allocated maintenance changes management documents initial requirement project infrastructure.
Alcatel-Lucent CDC Workshop, Coaching & Knowledge Transfer Project Management.
Business Systems Development SDLC and introduction to the Microsoft Solutions Framework Team and Process Models.
Web Trnsport – Beta Testing and Implementation TUG Roundtable Discussion Elizabeth Rodgers Info Tech, Inc. October 9, 2007.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
Project Workflow. How do you do it? -Discussion-
Project Tracking. Questions... Why should we track a project that is underway? What aspects of a project need tracking?
Distributed Software Development Transport4You1 Project Plan Gaurav Kushwaha & Dajan Zvekic.
T Iteration Demo Team WiseGUI I2 Iteration
© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 1 Agile Assessment Gadi Lifshitz, Ayelet Kroskin, Barak Yagour, Yael Dubinsky.
T Project Review X-tremeIT I1 Iteration
Steven Kolenda, Jacob Brown, Johnpaul Barrieau, Jen Bilotta, Felix Rohrer CS673 Software Engineering
KS3 Phase4 Client Server Monitoring System October 1, 2008 by Stephen, Seema, Kam, Shpetim.
AP-1 5. Project Management. AP-2 Software Failure Software fails at a significant rate What is failure? Not delivering it on time is an estimation failure.
Computer Science and Software Engineering© 2014 Project Lead The Way, Inc. Software Design Process.
Dr. Nguyen Hai Quan.  Why SCRUM?  What is SCRUM?  Some terms  SCRUM Meetings  Sprint  Estimation  Product backlog  Sprint backlog  Whiteboard.
Project Management Process Transition & Closure Project Management Process Project Description Team Mission/ Assignment Major Milestones Boundaries Team.
CSC 480 Software Engineering
CSPC 464 Fall 2014 Son Nguyen. 1. The Process of Software Architecting, Peter Eeles, Peter Cripss 2. Software Architecture for Developers, Simon Brown.
Timesheet training Version: Introduction Duration: 1.5 hours Purpose: Guide on how to use Timesheet.
T Iteration Demo Tikkaajat [PP] Iteration
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
CSE Senior Design II Day 1: Getting Organized Spring 2016 Instructor: Mike O’Dell.
TMP3413 Software Engineering Lab Lab 01: TSPi Tool Support.
1SEP Software / Web Engineering Projects 2IPE0 Spring Lou Somers.
How Software Projects Start SW projects start with a need. We need to keep better data on the students in the CSCE Dept. I heard that one of our competitors.
1 Development with Agile methodology Scrum Lifecycle DEVELOPMENT PROCESS IN DROISYS INC.
T Project Review Sotanorsu I2 Iteration
Software Quality Assurance Chip Ene, February 14, 2015.
Industrial Software Development Process Bashar Ahmad RISC Software GmbH.
Informed Traveler Program and Applications Agile / Scrum Overview Jerry Inberg.
Embedded Systems Software Engineering
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
T Project Review X-tremeIT I1 Iteration
Software / Web Engineering Projects 2IPE0
Scrum.
CSC 355 – Newer Approaches to System Development Life Cycles & Processes, Spring 2017 March 2017 Dr. Dale Parson.
Software Configuration Management (SCM)
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
IEEE Std 1074: Standard for Software Lifecycle
Product Backlog List of things that needs to be done to make the product come into existence 
Chapter 3: The Project Management Process Groups: A Case Study
Defining the Activities
AGILE METHODOLOGY MANAGE PROJECT USING AGILE SCRUM.
Scrum MODULE 3 – Part 3.
Software / Web Engineering Projects 2IPE0
Software Development In Agile
Software / Web Engineering Projects 2IPE0
SDLC (Software Development Life Cycle)
Software / Web Engineering Projects 2IPE0
Software Development In Agile
Presentation transcript:

1Lou Somers Software Engineering Projects 2IP35 Autumn

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

3Lou Somers General information n A real project n A real customer n A team consists of 8-10 students n Separate project and quality manager (students 2IP45) n Each team has an advisor (staff member) n Timing n Available time: 12 Ects  336 hours per person n Start: September 1, 2014 n Deadline: October 24, 2014 (eight weeks later) n Marking n General mark for group n Individual adjustment (peer reviews by group, managers, advisor)

4Lou Somers Organization

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

6Lou Somers Project planning

7Lou Somers Sprint planning

8Lou Somers Scrum

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

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

11Lou Somers Devils triangle We have n Fixed budget n Fixed time

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

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

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

15Lou Somers Customer presentations n Kees van Overveld n Michiel Seerden