Syllabus Overview
For students with the necessary prerequisites, the Digital Capstone is an opportunity for structured practice on integrating three key capabilities for any digital program: product management, application development, and analytics. This course is project-based with a set of three specific deliverables. The course experience is anchored in three primary activities: student review of learning materials to deepen their expertise, execution of project-based deliverables, and review/retrospective around said deliverables.
By the end of this course, you will be able to:
Move from design to code across multiple iterations
Design actionable observations into your digital deliveries
Integrate your practice of product design, application development, & analytics
CLASS DELIVERABLES
Your final team deliverable is a tested prototype for a particular user story.
The material we’ll cover in class is not intellectually difficult- you could spend a few hours understanding (in concept) everything we’ll cover in class. However, it is challenging to practice. Bright, energetic professionals like you spend whole careers just practicing and sharpening their ability in a few of these topics. For this reason, our emphasis is on short introductions, time for practice and collaboration in class, and then review of example submissions in class.
WEEKLY ASSIGNMENTS
Please complete the following with your team:
Team Charter: Please use this template and share it to ‘chaskell99@gmail.com’. Agile Team Charter. Likely, you’ve already done some or most of this prior to class, and it’s fine to reuse that material. Please make sure this version you submit reflects your most current thinking on the project and where you’d like to focus
Week [n] Backlog in Dev Journal: Please describe the work you plan to do in Sprint 2 by copying the Dev Journal template and filling out the material for Sprint 1. Please share the file to ‘chaskell99@gmail.com’.
OPTIONAL Kanban (Trello) Board: Please do this on Trello. Feel free to reuse boards and content from Trello, but make sure this version is current. Arrange your pipeline however you would like, but please make sure that you have at least the first two columns at the beginning of the board:
Product Backlog: as a repo. For all the ideas you’ve come up with and might want to work on.
Sprint Backlog: as the starting point for the content you’re working on in the current or upcoming sprint.
As you finish sprints, I’d like to see what you finished on each one. For this, you can use one of the following:
add a ‘done’ column in a single board for each sprint (Done-Sprint 1, Done-Sprint 2, etc.)
make a copy of the board with your product backlog for each new sprint and use that
Some other alt. that you prefer and we mutually agree is workable relative to the class infrastructure.
Please share the Trello board to ‘chaskell99@gmail.com’.