SE.3010./.3020./.3030. Course Overview
This course aims to build an open-ended system as a team, focusing on requirements from real customers, multiple viewpoints, new technical skills, and process improvement. It follows a structured framework with sprints, flex weeks, key policies on attendance, and use of Scrum methodology. The key roles include Project sponsor, Product Owner Proxy, ScrumMaster, Note Taker, and DevOps Lead. Emphasis is on continuous integration, gathering requirements, and maintaining Scrum artifacts.
Uploaded on Sep 08, 2024 | 0 Views
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. Download presentation by click this link. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
E N D
Presentation Transcript
Goals Build an open-ended system as a team Open-ended: requirements from a real customer Team: benefit from multiple viewpoints Learn new technical skills Experience with process; building on SE 2800 Apply Scrum: 3 sprints per quarter Later in the year: focus on process improvement Apply SE 3800, 3821 Continuous integration, gathering requirements Not co-requisites; if taken later, then it feeds the other direction
Structure Three 3-week sprint + 1 flex week SE 3010: flex week is the first week 1stweek: meet w/ PO, schedule ceremonies, start backlog Sprint 1: Primary user stories, storyboards, mockups Sprint 2: Design, software spike for entire solution Sprint 3: First releasable increment Final exam: project progress, lessons learned
Key policies Attendance required Lab time: only guaranteed meeting time, focus on ceremonies Unexcused absence: up to 1 letter grade cut Catalog: Lab and examination attendance is mandatory Excused absences: illness, school obligations (as approved by the VPA) Expectation: will communicate with team Tardiness: More than 10 minutes late; notify team & instructor Be sure to check in you may be marked absent! 3 or more times: grade penalties Leaving early: also a problem - get approval
Our framework Scrum Artifacts Product Backlog: Epics, User stories, Bugs/defects, Knowledge acquisition, Internal improvement Sprint Backlog: story-pointed PBIs with acceptance criteria Burndown Chart Scrum ceremonies Sprint planning Weekly stand-ups Backlog grooming: additional ceremony since don t have typical product owners Sprint Review Sprint Retrospective Artifact: a carefully written document w/ screen shots & evidence
Our framework: Scrum Roles Project sponsor: external customer Product Owner Proxy: One person will perform this all year (unless we decide to change) Primary conduit between team and sponsor Responsible for ensuring backlog maintained; has power to add items Arrange meetings, typically twice a sprint Represents sponsor when sponsor not available, especially for PBI validation ScrumMaster: Scrum coach, facilitator; rotate every other sprint Note Taker: ensures meetings, stand-ups documented DevOps Lead: ensures build, deployment instructions current; set up CI
Expectations No traditional exams, infrequent class-wide meetings 4 hours/week in lab, 6 hours/week outside work Lab time: largely performing ceremonies Also useful for knowledge transfer, discussing designs Expect me to visit each team at least twice important part of class Must log time this is expected at many companies Accuracy is important: helps improve estimates Log time in minutes hours are too low resolution If make a mistake, correct it Be sure to log your time within a couple days; won t remember details otherwise See FAQ on SDL Information confluence for more detail
Materials: Schedule See Fall 2019 Schedule Start logging with first week Note this and other class meetings are not logged helps with estimates Key throughout the term: Descriptive titles for PBIs so the title is enough on reports Consistent acceptance criteria Especially spikes: build GUI describes the goal, not when done And Knowledge Acquisition: cannot know all of Android development Give a goal in terms of something you can build Timebox configuring laptops; get help if needed
Grading Each sprint: 25% of your grade 40% process, 40% quality, 20% product Just building a working system is not enough process is a major goal Remaining 25%: overall contribution, additional deliverables Time logs must be accurate Fabricating participation is academic dishonesty Accuracy is important for teammates, future estimation Review syllabus
Space Details Pick your cubicle; north one is quiet but can get chilly in winter Inner glassed-in room: meetings, especially with customers Can lock cabinets We provide locks; if bring your own, we should have the combination Ensure locks fit easily broken handles take forever to get fixed 24/7 lab card access check! Note: must have at least two in the room from 10 pm to 7 am for safety Show up ready to work no 15-minute settling in time If need to eat, bring a snack; runs to Skylight Caf chew up time Ok to use fridge keep it clean Each area: 5 chairs, 1 large screen, several small screens Respect whiteboard must share with other sections
Tools Jira: primary project tracking Confluence: team workspace, process artifacts Project artifacts: in repository Google docs: must copy materials back to Confluence Repository: Bitbucket unless your instructor approves alternative Instructor will create the repository
Tools, continued Jenkins, TeamCity: continuous integration tools VMs for development: sdlstudentvmXX.msoe.edu Will have root access; install own tools An opportunity to learn a bit of Linux! Slack, other communication tools: team preference Expectation: everyone checking at least once per day, likely more often
First Week Set up Confluence page Project name, team members/email, client contacts One or two sentence project goal Each team member: pictures on Confluence, Jira, Bitbucket Set up page for meeting notes Create Jira PBIs for first sprint note the sprint naming convention Log time to tasks First PBIs: creating artifacts
