• Save
Research instruments case study
Upcoming SlideShare
Loading in...5
×
 

Research instruments case study

on

  • 1,895 views

 

Statistics

Views

Total Views
1,895
Views on SlideShare
1,765
Embed Views
130

Actions

Likes
0
Downloads
0
Comments
0

4 Embeds 130

http://agileonthebeach.com 68
http://www.agileonthebeach.com 54
http://www.agileonthebeach.co.uk 7
http://cache.historious.net 1

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Research instruments case study Research instruments case study Presentation Transcript

    • Our Agile Journey Research InstrumentsClick to edit Master subtitle styleRob Thompson
    • Company BackgroundResearch Instruments (RI) providessystems which are used in fertilitylaboratories (IVF)Based in FalmouthEmploying 60+ people70 distributors providing coverage in 60countries
    • Technologies and StandardsWindows software – C#, SQL, WPFEmbedded C on microcontrollersElectronics hardwareMechanicalISO 13485 – Medical Device DirectiveFederal Drug Administration (FDA) 21 CFR 820
    • Our OLD process
    • Our Agile Journey – so far2 day workshop ‘Kanban’ board Sprints (2 week) Test Driven Development Pair Programming
    • User Story DevelopmentAs a User I would like the software toremember my settings so that I don’thave to re-calibrate and re-configurethe software each time I use it. As an Embryologist I would like to be able to replay stored videos of procedures so that I can see how they were performed As a Patient I would like to see confirmation that both me and my embryo have been identified correctly so that I can relax and feel confident
    • Magic Board
    • Graphs !! Development Effort
    • The BenefitsTeam enthusiastic, focused, motivatedEncourage changes in requirementsEasier managementHigher qualityPredictability + FlexibilityIdentify problems quickly
    • Outside the dev teamOther teams want to adopt Agile principlesQuality dept is happierSnr Management have graphs to play withMarketing speak the same languageCustomers given accurate timescalesDevelopment process is simple
    • Myths / PreconceptionsIt’s for large teams / small teams / sw houseIt’s undisciplined / chaoticIt’s not compatible with quality systemsIt’s for software developers
    • Conclusions…Cannot introduce Agile without helpAgile is a journey, not a destinationEncourages/requires change in cultureWe would never look back