1 / 16

ITEC 370

ITEC 370. Lecture 24 Lifecycles. Review. Questions ? Grades for Requirements/Design Doc F give prototype demonstration Testing plan for your software Maintenance Business aspects Scenarios. Objectives. Life cycles Beyond the waterfall…. Questions.

marius
Download Presentation

ITEC 370

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. ITEC 370 Lecture 24 Lifecycles

  2. Review • Questions? • Grades for Requirements/Design Doc • F give prototype demonstration • Testing plan for your software • Maintenance • Business aspects • Scenarios

  3. Objectives • Life cycles • Beyond the waterfall…

  4. Questions • What are the disadvantages of using the waterfall method (what we have done in class)? • What are some of the advantages?

  5. Differences • There isn’t one way to develop software • Each has advantages and disadvantages • Team, client • Examples • eXtreme programming • Scrum • V model • Spiral • Evolutionary model • Lean

  6. Scrum • Roles • Core (Owner, Dev Team, Scrum Master) • Ancillary (Managers, Stakeholders) • Development is made up of sprints • One week to one month duration

  7. Sprints • Purpose it to create a portion of the product • What is created comes from the backlog (list of requirements) • Owner determines priority of what is implemented • Team determines how many can be implemented • Backlog cannot be changed during a sprint

  8. Meetings • Daily scrum • Every dev member comes prepared to give an update • Start on time, no waiting • Same location, same time (habits!) • Length is set (15 minutes) • Questions • What did you do yesterday? • What are you going to do today? • What roadblocks are you encountering (Scrum master)

  9. Meetings • Backlog grooming (done by devsduring sprints) • Work on granularity • Work on prioritization (developer not owner) • Set things up for owner to decide what is to be done next • An hour at most

  10. Meetings • Scrum of scrums • After daily scrum • Sub group of people together • Questions • What has the team done since last time? • What is the team going to do now? • What is slowing the team down? • Are you going to slow another team down?

  11. Meetings • Sprint planning meeting • Beginning of every sprint • 8 hour meeting • 4 hours – Everyone – priorities for the backlog • 4 hours – Dev team creating plan for sprint

  12. Sprints • Review / retrospective meeting • 4 hour meeting • What went well? • What should be changed for the next time around? • Demonstration of accomplished work to stakeholders • No incomplete work can be shown (no demo is better than a bad demo)

  13. Artifacts • Product backlog • Sprint backlog • Increment • The piece of software (cumulative through sprints) • Burn down • Chart showing what has been done and what is left

  14. Others • Backlogs • Typically have a requirement and a user story • Feature description • Spike • X amount of time to research / create a prototype • Epic • Group of user stories • Tracer bullet • Creating code within current architecture • Definition of done • Velocity • How many points can be done in a sprint? • Abnormal termination

  15. Relationship to waterfall • Requirements • Design • Implementation • Testing • Maintenance • Sprints • Meetings

  16. Review • Reactive • Active

More Related