1 / 10

Agile Library Development

Agile Library Development. Going from a Void to Chaos is still Progress. Process Overview. Strategic Planning (Individual Leaders) List scenarios and user stories . Prioritize user stories internally to project.

virgo
Télécharger la présentation

Agile Library Development

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. Agile Library Development Going from a Void to Chaos is still Progress.

  2. Process Overview • Strategic Planning (Individual Leaders) • List scenarios and user stories. • Prioritize user stories internally to project. • Write top user stories onto Index Cards (Story Cards) & Bring to Prioritization & Planning Meeting. • Prioritization & Planning (All Leaders) • Estimate Story Card difficulty and importance on the planning board. • Re-factor Story Card requests as necessary to refine into testable features & deliverable items. • Order all Story Cards by relative importance/priority from top (highest) to bottom (lowest). • Iteration Planning (Leaders/Developers) • Start at top of priority Stack break each Story Card into Tasks and write onto a Task Card. • Use planning poker to collaboratively estimate Story Points needed for each task. • Continue estimation of tasks until all Story Points for that iteration are spent. • Return remaining Story Cards to Leaders. • Move Story Cards to Iteration Board and Code. • Iteration • Each developer grabs a task, puts their name on it and moves it to the . • Code task and when complete moves it to the Done • Delivery • Deploy code with completed Stories to staging server. • Send cards to testers for testing. • Return incomplete Story Cards to Leader.

  3. Some Information about Iterations • Two work weeks of 9 optimal days with one day for Iteration Planning. • Our capacity to develop during an iteration is represented by “Story Points”. • Story Points vary iteration to iteration depending on how much programming time is available in the department. • Every User Story or Feature request is broken down into tasks and each task is estimated in terms of it’s difficulty in Story Points. • Once the estimated difficulty of tasks reaches the number of Story Points for an iterations we stop and move the tasks to the Iteration Board.

  4. Iteration Scheduling Iteration 1 Planning Iteration 1 Iteration 1 Iteration 2 Planning Iteration 2 Iteration 3 Planning Iteration 2

  5. Planning & User Stories Lets Go! Split or Simplify Unclear? Define Better Priority • Leaders bring stories on Story Cards • Use board to figure refine stories • Stack Story Cards top to bottom in priority highest to lowest • Remaining Cards are returned to Leaders Needs some Discussion Drop! Difficulty

  6. Story & Task Cards

  7. Determining Story Points Available • Each Developer contributes 1 Story Point per day they are available. • 1 SP roughly equals an “I can get this done by the end of the day” level of effort. • Each Devs contribution has to be modified by how much actual time is taken away by other duties. (∆) • Vacations and other adjustments may cause Story Points to vary per iteration.

  8. Real World Stories & Tasks (Systems) A script can read all SSL certificates on a server and email an alert 30 days prior to expiration. Write a script to convert existing videos to streaming format. (GDE) A site visitor can play videos in Streaming format. (Primo) As a user I can discover books stored in the Repository in electronic format. Modify upload script to convert videos to streaming format on upload. (EUCLID) Storage Library staff can create pseudo borrowers through a web form. Run streaming conversion script over existing videos (StaffWeb) An admin can migrate previous StaffwebDrupal Accounts to LDAP based accounts.

  9. Real World Stories & Tasks (Systems) A script can read all SSL certificates on a server and email an alert 30 days prior to expiration. Write a script to convert videos to streaming format. 5 (GDE) A site visitor can play videos in Streaming format. (Primo) As a user I can discover books stored in the Repository in electronic format. Modify upload script to convert videos to streaming format on upload. 3 (EUCLID) Storage Library staff can create pseudo borrowers through a web form. Run streaming conversion script over existing videos. 1 (StaffWeb) An admin can migrate previous StaffwebDrupal Accounts to LDAP based accounts.

  10. 11/11/07 45 S1 – Task 1 S1 – Task 2 S1 – Task 3 S2 – Task 1 S2 – Task 2 S2 – Task 3 S2 – Task 4 S3 – Task 1 S3 – Task 2 S3 – Task 3 Drop Outs 

More Related