1 / 5

Lean Methodology Theme #0 - Introduction

Lean Methodology Theme #0 - Introduction. Richard Bruskiewich Crop Research Informatics Laboratory International Rice Research Institute. What is Theme #0? What tools does it contain?.

randolph-tripp
Download Presentation

Lean Methodology Theme #0 - Introduction

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. Lean MethodologyTheme #0 - Introduction Richard Bruskiewich Crop Research Informatics Laboratory International Rice Research Institute

  2. What is Theme #0? What tools does it contain? • This theme discusses the principle of applying lean methodology to software engineering projects. It is composed of the following tools: • Eliminating Waste • Amplifying Learning • Deciding as late as possible • Deliver as fast as possible • Empower the team • Build integrity in • See the whole

  3. How are we already applying theme #0 principles in our projects? • We are using CVS to synchronize development • We are designing some of our software with a common domain model (ICIS; GCP).

  4. Recommendations to apply theme #0 to our projects? • We need to better define our value stream and attempt to streamline activities accordingly • We need to have more end user feedback based on usable prototypes; develop a more iterative design process • We need to concurrently explore a wider range of options as solutions to technical issues • We need to commission a regular platform deployment process • The team should meet weekly to set a small number of SMART objectives for the week • End user perception of our user interfaces should be assessed. We should develop enhanced but simple documentation for our target use cases, models and APIs

  5. Proposed Objectives and Timetables • Today, in discussion: document our value stream on the white board/Wiki • Monthly: convene a GCP end user feedback meeting to present and discuss platform prototypes • By the end of this week: Create an Eclipse Java project for a GCP platform bundler/publication + end user platform installer (setup.exe kind of tool for the GCP platform) and use it to deploy a baseline downloadable package for the GCP platform • By the end of next week: Clean up the GCPWiki use case inventory for the GCP platform; extract a set of priority features for design and implementation, and load these into CropForge feature tracking, for assignment to developers • Initiate regular Monday 8:00 am GCP project meetings, with video conference connection to CIMMYT (CIP?) to briefly report on progress, discuss problems and decide major project work objectives for week, but let developers use CropForge feature tracking mechanism to select use cases for weekly implementation

More Related