SE3191:Welcome to the SDL

Winter 2013-2014Dr. Rob Hasker

Dr. Mark Hornick

SDL = SE2030 + SE2800 + SE2832 + SE3821 + real project

Pulls many previous courses togetherProjects are large with both short and long-term deliverablesRequires real-world practicesBuilds teamwork skillsUses real-world processes

With some learning-specific adaptations

Predefined process frameworks help teams work togetherScrum is a framework that is characterized by:

• Short development cycles (sprints)

• Dedication to performance and quality

• Self-directed teams/shared responsibilities

• Process discipline

• In SDL, not all Scrum elements are reproducible• Product owner

Project sponsor/stakeholder

• Scrum Master Instructor

• Shared Responsibility Specialization

• In SDL, we also include additional process elements not always found in classic Scrum:

– Instructor mentoring

– Roles/Responsibilities (more later)

– Grading

Planning & Reporting– Atlassian Jira

What do you produce? Product

• Code • Tests• Documents

Project • Plans• Designs• Reports

Process• Time/work logs• Retrospectives• Status Updates

People

• Emails/Communication• Minutes• Reviews (Code etc)

Grading PolicyProcess

This part of your grade is based on how well you work within the context of the SDL Agile framework.

40%

Project and ProductThis part of your grade is based on what you produce. 40%

PeopleThis part of your grade is based on how productively you use SDL time andbeing an effective team member.

20%

Total 100%

See the SDL Grading page on Confluence for details

Attendance PolicyConsider the SDL as a work environment, where attendance, timeliness, and productivity are important.– Unexcused absences are not permitted unless you clear

them with your instructor beforehand.• If you don't show up for SDL, you may be "fired".

– Arriving late to the SDL or leaving early must be approved by your instructor.

• Chronic (repeated) lateness or truancy will affect your grade negatively or result in a failing grade.

• If you are late, you will be marked “absent” until you take action

• You are required to notify your team (via the team email address) of any lateness or absence.

How to succeed in the SDLCommunicate

– Ask questions– Always make sure others know what you are doing

Discipline– Meet your weekly and long-term deliverables

• On-time• When you’re in the SDL, your “at your job”

Hard work– This class is just as important as others– MSOE culture = 3-4 hrs/credit, or 9-12 hours/wk for SDL

• You must contribute equitably to your team’s project

Work in the best interests of your team and sponsor

MeetingsLab meetings

– Infrequent and short – Address team-wide issues/questions/concerns

Instructor meetings– Weekly– Meeting minutes have to be posted on Confluence

Daily Scrum meetings– Every time you meet– Weekly Status reports have to be posted on the Confluence wiki.

Stakeholder meetings– As specified by the sponsor/stakeholder or as needed.– You will be responsible for arranging these, but get help from your instructor when you

have problems.– Meeting minutes have to be posted on Confluence

Logistics and Tools 24/7 card access to SDL

Verify that you have access Altassian JIRA/Confluence

msoese.atlassian.net Git/Bitbucket for DVCS

bitbucket.org Jenkins/TeamCity for build

opaldev.msoe.edu:9090/jenkins teamcity.msoe.edu

VM’s for development url’s specific to your team/project You need to install any tools specific to your

project (C++, PHP, Python, C#, Tomcat, Rails, etc.).

You’ll be given shell access You need to learn some linux