T Software Development Project I Customer Info Jari Vanhanen Ohjelmistoliiketoiminnan ja –tuotannon laboratorio Software Business and Engineering Institute (SoberIT)

T Agenda :15 – 16:55 Info for customers 17:00 – 19:00 Topic presentations 19:00 – 19:45 Free discussions between customers and students

Roles  Customer  provides the topic and system requirements  helps with technical issues  takes the responsibility of the system after the project  Project group  3 software engineering experts  project manager, QA manager, architect  5 developers  develops the software  Mentor  ensures the fulfillment of the educational goals  helps with working methods

Support for the Projects from the Course  Process framework  Mentoring  Experience exchange sessions  Some sw&hw infrastructure  Grading and feedback  Participation in iteration demos  Accenture  Quality Award  “Ask Accenture” – service

Legal Issues  Intellectual property rights (IPR)  1. open source  2. customer gets IPRs  Non-disclosure agreement (NDA)  must be mentioned in the topic proposal  Contracts prepared by HUT lawyers  HUT companies  HUT students  Public documentation  except code and technical specs  if the customer requires NDA she must review documents before publication  3000e (+VAT 22%) participation fee for industrial customers  charged in late October

Software Process – Special Challenges  New team and organization -> process must be planned from scratch and communicated to everyone  Physical distribution -> special care for communication and project visibility  Temporal distribution -> you can’t keep everything in your head-> documentation overhead  Project is done for an external customer -> requirements engineering during the whole project  Software will be maintained by other people ->knowledge transfer

Infrastructure from HUT  Hardware  several computer classes at HUT  Software  HUT provides lots of software in computer classes  Microsoft MSDN AA  MagicDraw UML Tool  Servers at HUT & SoberIT  CVS – version control  Bugzilla – bug reporting  MediaWiki – collaboration  Customer must provide other necessary hardware/software

Software Process – Framework  Process framework provided  iterative  phasing and schedule fixed  enforces certain good work practices and crucial documents  allows lots of freedom (and responsibility) for customization

Software Process – Project Control Variables  Quality ”fixed”  high quality recommended  some alleviations to carefully selected quality aspects are allowed if that is what the customer wants  Calendar time fixed  project schedule defined by the course  major control points such as iteration demos  Effort fixed  150h/person (+15-40h if substituting T with T T )  includes some course related work, but everything contributes to the project in some way  Scope flexible  adjusted depending on the groups’ skills and knowledge of the problem domain

Software Process – Typical Effort Distribution

Software Process - Iterations

Software Process - Iteration Planning  Group and customer plan each iteration’s goals and deliverables  goals are higher level ideas of what is expected from the iteration  deliverables include software units and documents to be created/updated  Iteration planning meeting  customer selects and prioritizes what is implemented based on  business importance  group’s effort allocation for the iteration  group’s rough effort estimates for implementing sw units  group’s estimates about architectural impact  Group concretizes goals and deliverables into required tasks  re-planning, if task effort estimates and allocated resources differ largely

Software Process – Iteration Demo  Arranged in the end of each iteration  , ,  exact times (8:00-18:00) published in early October  at SoberIT (Innopoli 2, 4th floor, Tekniikantie 14)  Participants  all project stakeholders + teacher, other personnel from SoberIT, Accenture  Group presents  project status (10-15 min)  iteration’s results including sw demo (20-25 min)  Customer evaluates the work performed  prepare in advance!  private discussion about the given points with the mentor after the demo  give comments about your evaluation to the group Tip! Arrange the next iteration planning meeting right after the iteration demo.

Software Process – Controlling the Projects  Arrange regular meetings  especially early in the project  Demand some regular reporting  Give concrete feedback

Software Process – Project Management

Software Process – Required Documentation  Required project documents  project plan  including QA plan and description of work practices  requirements document  technical specification*  user’s manual*  QA reports  progress reports (a slide set for the iteration demos)  final report  Course provides some document templates  their use is mandatory, but irrelevant topics can be omitted *the course sets no requirements on the content or format of these documents

Software Process – Requirements Engineering

Software Process – Design and Implementation

Software Process – Quality Assurance

Evaluation – General  Customer evaluates  intermediate and final results, and working methods  mentor ensures the objectivity of the evaluations  realistic expectations  Mentor evaluates  working methods  Group members evaluate  personal contribution of the other group members

Evaluation – Iterations (Customer)

Evaluation – Project’s Results  Customer  compares to the original/updated project goals  manage customer’s expectations in project planning and during the project  Mentor  compares to typical projects on this course  difficulty of the project +/- a few points

Customer Satisfaction

Project Topics – Selection Process  Students have formed 15 groups  3 SE experts + 3 developers  teacher adds 2 developers  A group contacts 2-4 customers  Groups appreciate  customer’s commitment to the project  customer’s domain understanding  provided infrastructure  provided technical guidance  realistic description of the expected skills from the group  Customer can choose any of the interested groups  if someone didn’t already take them  be quick!  If you get a group  inform the teacher and he will remove the topic from the list  If you don’t get a group by tomorrow evening  inform the teacher and he will highlight your topic on the list

Aihe-esitykset  Esitykset 5 minuutin välein  jos puristaa allr 5 minuuttiin, niin voi ottaa 1-2 lyhyttä kysymystä  pidemmät vastaukset klo 19 jälkeen  Seuraava esiintyjä lavalle samalla kun edellinen vastaa kysymyksiin