Scrum (an agile method) as practiced by MyUW
Developing
- Scrum
- Agile
- project management
- product management
Abstract for Print (1000 characters maximum):
Please provide a print-ready description of your session for conference attendees. A good description will explain the purpose of the session, the content that will be covered, and the outcomes that attendees will take away from your session.
Explanation of Scrum as practiced by the UW-Madison MyUW Infrastructure team. A case study of a real-life application of an agile method in higher education, with some lessons learned and resources to learn more. (This session follows up on 2014's session http://lanyrd.com/2014/apereo/sdbbcc/ , but with more focus on agile methods and less focus on technical practices.)
Higher education IT is occasionally pressured to be "more agile". What does agile mean? What does it take to practice Scrum for real? What might happen if you do?
Session attendees will gain one more example for understanding the potential of agile methods, and one more contact for learning more and continuing to compare notes on how we practice higher education IT.
This is an optional field available to provide you the opportunity to speak directly with the program committee. Explain your motivation to offer this event, the audience that will be served, how you will engage and interact with the audience, and any additional evidence or detail that did not fit into the print abstract that can help the committee evaluate the merit of your session.
Higher education IT is continually pressured to adopt "agile", sometimes without context on what this means and how it relates to larger IT and University organizations with a decidedly non-agile waterfall bent. The MyUW Infrastructure team is an example of a within-higher-education-IT team practicing an agile method with relative maturity and to good result. This can serve as an illuminating example, a reference, a clarifying checkpoint on what Scrum is, what it requires, and what it delivers.
- Developer
- Documentation
- Integration
- OpenSource
- Other
- Beginner
Nothing special.
"presentation"
Conference session presentations will run for 45 minutes with an open format. Presentations can be information sessions, panel discussions, or other speaking events. For information sessions, we recommend 30 minutes for the presentation and 15 minutes reserved for audience questions and answers. We DO NOT require presentations to center on Apereo products or projects. When developing presentations, please consider the issues, opportunities, and innovations that are most central to best practices, fundamental values, and/or success in technology-enabled teaching, learning, and research.
- Andrew Petro, andrew.petro@wisc.edu, Product Backlog Manager - MyUW - Division of Information Technology, UW-Madison