466 9754 [email protected] Tonight’s class • Start up • CI, CD, DevOps: Jez Humble, guest lecturer • Project • Part 1: Team formation and product development launch • Part 2: Sprint 1—deliver a real product increment (due Nov 16) • Wrap up
466 9754 [email protected] Are you here tonight? • Type something in the Chat window so I know you’re here. • This is one way for me to gauge your attendance and recognize your class participation. Image: http://blog.pluralsight.com/pluralsight-top-10-building-a-great-software-development-team
466 9754 [email protected] Project overview • Project assignment: • Design, implement, and deliver a real software product • with a real Scrum team • for a real stakeholder Image: http://www.mobileqazone.com/profiles/blogs/post-release-software-product-support-and-regression-testing, 2015-10-18
466 9754 [email protected] Project overview • Part 1: Team formation and product launch (due Nov 2) • Part 2: Sprint 1—deliver a real product increment (due Nov 16) • Part 3: Sprint 2—deliver another real product increment (due Nov 30) • Part 4: Sprint 3—deliver the final product increment (due Dec 14) Image: http://www.livescience.com/51000-cucumber-nutrition.html, 2015-10-05
466 9754 [email protected] Project part 1 • What’s due (during class on Nov. 2) • 5-minute team presentation • Who are you? What are you building? Who are you building it for? What are your top PBIs?
466 9754 [email protected] Project overview • Part 1: Team formation and product launch (due Nov 2) • Part 2: Sprint 1—deliver a real product increment (due Nov 16) • Part 3: Sprint 2—deliver another real product increment (due Nov 30) • Part 4: Sprint 3—deliver the final product increment (due Dec 14) Image: http://www.livescience.com/51000-cucumber-nutrition.html, 2015-10-05
466 9754 [email protected] Project part 2 • Sprint 1—Deliver a real product increment (due Nov 16) Image: http://www.romanpichler.com/blog/the-definition-of-ready/, 2015-11-01
466 9754 [email protected] Project part 2 • What’s due (before class on Nov 16) • Add documentation to your GitHub repo: • URL of your working product increment (could be the actual product or a video of your working product increment) • Code • Committed in Github • Written using pairing/mobbing and TDD, with at least 10 tests, and all tests are green • Adequate code coverage, with evidence of the code coverage • An automated build system modeled on Continuous Delivery. At least: when you commit to master, all tests run and all tests are green.
466 9754 [email protected] Project part 2 • What’s due (in class on Nov 16) • 5-minute team presentation (like a Sprint Review) • What did you get done? Show us a brief demo. • What feedback did you get from your stakeholders? How did it change your product backlog? • What do you plan to deliver in the next two sprints? Image: https://agilepetergoodall.wordpress.com/2014/08/29/working-in-agile-showcasing-work-and-incorporating-feedback-the-sprint-review-meeting/, 2015-11-01
466 9754 [email protected] Were you here tonight? • Type something in the Chat window so I know you’re here. • This is one way for me to gauge your attendance and recognize your class participation. Image: http://blog.pluralsight.com/pluralsight-top-10-building-a-great-software-development-team
466 9754 [email protected] Tonight’s class • Start up • CI, CD, DevOps: Jez Humble, guest lecturer • Project • Part 1: Team formation and product development launch • Part 2: Sprint 1—deliver a real product increment (due Nov 16) • Wrap up
rkasper
matleenalaakso
pylapp
junghyeonjae
ohmori_yusuke
wingnus
signer
s3i7h
masatatsu
danielanewman
tanoku
hannesfritz
smashingmag
palkan
aki_iinuma
eileencodes
jponch
jeffersonlam
garrettdimon
brianwarren
