ZIMS World Tour Podcast

Welcome to the ZIMS podcast - a seven-minute tour of the ZIMS world. This episode takes you behind ZIMS screen development and into the ZIMS database.

Click on the "play" arrow in the center of the screen below.

Sprint 1 / Week 1 results

Under our new development process our stated goal was to complete development of fifteen screens per week. Last week (the first week of actual code-writing) we completed a total of eighteen screens. This is a very good start.

(What’s a Sprint?)


Sprint 1 focuses on Institution screens - in many ways the least dramatic screens in ZIMS. But it is in this sprint that we will also create many templates that will be reused throughout ZIMS.

Sprint 1 contains approximately forty-five screens. Release 1, due out March 1, 2010, will be built in seven sprints and will have a total of approximately 300 screens and reports.

Meet the ZIMS Team

Below: Craig Yellick, ISIS ZIMS Team Leader,

introduces the new A-1 team to ZIMS architecture

and the new development process.

Gurgaon, India: ZIMS Sprint 1 is moving fast. (What’s a sprint?)

We want to introduce you to the team building ZIMS. Click here for photos and brief bios of the five ZIMS Project Team. With an impressive array of deep experience in the IT industry and the zoo and aquarium business, these pros are guiding ZIMS toward completion.

A-1 Technology, the new ZIMS vendor in Gurgaon, India has assigned its finest developers to the ZIMS project (because ISIS insisted on it). The A-1 developers are split into three teams, led by Gurmeet Badwal (Scrum Master), and Rishun Gupta (Project Coordinator).

Team Shark, Meenakshi Sharma (Team Lead), Sarvedra Singh (Backup), Umang Kapoor, Prateek Gupta.

Team Tiger: Tarun Sainger (Team Lead), Ritu Dadarwal(Backup), Firoz Alam, Ravikant Mahajan, Neeraj Prashar

Team Dragon: Kaushal Bajaj (Team Lead), Ritesh kumar(Backup),Vishwanathan, Ritu Bhadwar, Suprodeep Mukherjee

For the next three weeks, Sprint 1 focuses on Institution screens including contact methods, staff, and ISIS Membership data. It’s probably the least sensational data in ZIMS and that is why we begin with it. This means we will have improved our processes, tools, and quality assurance methods before we get to the most-critical parts. Also, we will be creating many of the re-usable templates, or “web parts” in this sprint that will make their way into all of ZIMS.