Dr. Rob Hasker

A new process: YOGA  10 Principles 1. Ignore the past, only look ahead 2. Be artists, free to create 3. Meditate on code each day: what to fix? 4. Daily meeting: discuss meditation results 5. Flexibility: choose a change of the day 6. Rotate often: switch roles for flexibility 7. Strengthen your core: exercises for the developers that make 80% of all changes 8. Improve balance: one foot stance at mtg 9. Salute the sun: celebrate yesterday’s changes, ensure enough food and coffee to for the day 10. Relax: stop thinking about code, chant UUUMMMLL

A new process: YOGA  10 Principles: 1. Ignore the past, only look ahead 2. Be artists, free to create 3. Meditate on code each day: what to fix? 4. Daily meeting: discuss meditation results 5. Flexibility: choose a change of the day 6. Rotate often: switch roles for flexibility 7. Strengthen your core: exercises for the developers that make 80% of all changes 8. Improve balance: one foot stance at mtg 9. Salute the sun: celebrate yesterdays changes, ensure enough food and coffee to for the day 10. Relax: stop thinking about code, chant UUUMMMLL You only Go Ahead SIGSOFT, July 2015 David Weiss

Logistics  Class roster, attendance policy  Book, Schedule, policies, grading  Course web site  Prereq check: SE 2800, Software Process I SE 2832, Verification

Curricular Context

Course Goals  Build on SE 2800: increase knowledge and skill in following software process  Tailor software process (especially Scrum) to project needs  Add continuous integration, verification, software quality components  Industrial strength tool use

Course Goals  Build on SE 2800: increase knowledge and skill in following software process  Tailor software process (especially Scrum) to project needs  Add continuous integration, verification, software quality components  Industrial strength tool use

Textbook  Scrum Shortcuts without Cutting Corners Ilan Goldstein, Addison Wesley, 2014 “an approach rather than the approach to implementing Scrum.” (p. xix) Scrum is a framework; organizations can and must specialize to their needs Key questions: what’s mandatory? What can we change and still be effective?

Tools  Atlassian JIRA/Agile planning & tracking Confluence (wiki)  Bitbucket Git repository Sourcetree  JUnit Test automation  Jenkins/Teamcity Continuous build

The big picture  1 st year: implementation  2 nd year: basic elements of SE process  3 rd year: project experience This course: software quality goals and tools, tailoring process to project

Scrum Refresher  Who are these people? Product owner ScrumMaster Development team

Scrum Refresher  Who are these people? Product owner ScrumMaster Development team What will be developed, and in what order Guiding team on creating, following process; removing impediments 5-9 people: determines how to deliver what product owner requests.

Scrum Refresher  Who are these people? Product owner ScrumMaster Development team  Is the product owner the only interface to the customer?  How to qualify as ScrumMaster?  How to approach being ScrumMaster? Scrum Team

Reviewing Scrum Activities  The Scrum process cycle (picture) Pair Exercise

Reviewing Scrum Activities  The Scrum activity cycle Sprint planning Sprint execution Sprint review Sprint retro- spective Daily scrum

Reviewing Scrum Activities  The Scrum activity cycle Sprint planning Sprint execution Sprint review Sprint retro- spective Daily scrum What are some issues that this does not clarify? Are there places where you did things differently on your internships? What needs to change about Scrum for SDL?

Product Backlog  Product backlog items (PBIs)  What qualifies as a PBI?  Who manages these?  What is “grooming”?  How are PBIs ordered?  How are PBIs estimated?  Differences on internships?

Course themes  What is Scrum, exactly? What can we change What are things we want to not do?  How would you introduce Scrum to an organization?  How to improve your use of Scrum

Other topics  Are there other ways to develop software?  How can we solve the “it works on my machine” problem?  Can we get customers to write some of our tests?  How to ensure the development environment is the same as the production environment?

Scrum review  Product roles  Scrum activities  Product backlog  Read: Ch. 2, 3 At start of Wed. class, submit hard copy, typed report on assigned Ch. 3 principle (Shortcuts 7-9) Heading: student named, assigned principle Definition: what assigned component means with examples Assess: reasoned opinion of value & correctness of each component; exceptions?

SE 2800 Review  What do you remember from SE 2800? Process models? Software development activities? Scrum process? Teamwork issues?  What do you think wasn’t precise in 2800? Pair Exercise

SE 2800 Review Review/retrospective

Practice vs. Process  Practice = “what we do” Analyze requirements, create architectural/design solutions, implement, verify  Process = “how and when we do it” Plan, organize, measure, make/meet commitments, ensure quality, control, improve, adapt

Activities  Planning & tracking  Risk assessment and mitigation  Requirements analysis & specification  Architecture and high- level design  High level design review  Detailed design  Detailed design review  Implementation (coding)  Code review/inspection  Unit testing  Integration testing  System testing  Acceptance testing  Deployment There are many different ways to organize these activities, but all must be included.

Process Models  Frameworks for organizing development activities  One pass, sequential – waterfall  Iterative/incremental Agile: XP, Scrum, Feature-driven development Personal Software Process/Team Software Process (SEI)  Highly prescriptive Cleanroom, formal