Agile Working Group Welcome! 1

Agenda Introductions – 20 min –Name –Role on agile team –What you hope to gain from being part of this workgroup Objectives –Steering Committee & PDF Objectives for Workgroup – 5 min –Team Norms – 20 min –Communication Strategy – 20 min –Break – 5 min –Workgroup Vision Template – 40 min Next Steps – 10 min 2

Introductions – 20 min 3

Steering Committee & PDF Objectives – 5 min

Steering Committee Objectives Document what is working or not working in Agile. What are the gaps? How can we share information about what is working or not? Assess whether we are doing Agile the same way or not across groups. Identify level of adoption and of maturity of Agile practices. Recommendations of how to apply Agile smarter instead of working harder. 5

Project Delivery Framework – Big Group Kickoff Meeting Requests made pertaining to Agile: –Would like ongoing Agile support and resources (3 votes) –Allow different flavors of Agile (1 vote) –Standardize Agile (1 vote) Requests from the PDF Co-Chairs: –Log onto UserVoice and share your comments / opinions: –Look over notes from the kickoff meeting https://sites.google.com/a/g.harvard.edu/pdf-big-group/home/notes –Keep them posted on any follow-up we’d like them to bring to the PDF big or small group pertaining to Agile 6

Team Norms – 20 min

Team Norms Roles & Responsibilities: Define How do we want to accomplish the objectives of the steering committee? –Meet, delegate, reconvene, and review; –Delegate, communicate electronically; –Other Should we have regularly scheduled meetings? –How often; –How long How should we communicate with each other between meetings? How should we delegate work? How should we keep each other informed of progress? Are there any other team norms we’d like to talk about / agree upon? 8

Communication Strategy – 20 min

Communication Strategies How would we like to communicate with HUIT at large? –OpenScholar website; –Confluence; – list; –Other How should we gather information to meet the steering committee objectives? –Team Interviews; –Electronic Survey; –Discussion Board; –Other Anything else around external communication we should discuss? 10

Break! – 5 min

Working Group Vision Template – 40 min

Provide core teaching and learning technologies to all Schools Support pedagogical innovation and research on learning Establish strong Harvard community based on actual partnerships with faculty and with academic support professionals Cultivate open source community around component development that complements core technologies Deliver high-quality program on time, on budget, in scope Strategic ObjectivesGuiding PrinciplesKey Performance Indicators Communicate and socialize program across the University Balance need to move quickly with thoughtful planning Seek early and continuous faculty input from across the Schools Transition program to ongoing services with sustained community and sustained vision Embrace fluidity Full-time staff focus is the rule; divided time is the exception University migration from previous platform(s) to core technologies Usable data from teaching and learning activities available for research Meaningful engagement with faculty / teaching teams and with academic support professionals around needs Harvard-specific technology enhancements and applications generated by open source community Program delivered on time and on budget Provide a continually evolving set of faculty-friendly, student-focused technologies that support teaching and learning across all Harvard schools, facilitate pedagogical innovation, and contribute to educational research. The Vision Example 1: Teaching & Learning Technologies

To reduce the cost for the delivery of Information Technology services for Harvard University To reduce error, rework, and security risk in the implementation and maintaining of infrastructure To develop a service catalog that defines optimized offerings and how services are defined, approved, funded, enhanced, and retired To improve the reliability and resiliency of HUIT service offerings To enable greater agility and efficiency in the delivery of HUIT services Strategic ObjectivesGuiding PrinciplesKey Performance Indicators Drive operational accountability through process enablement The future state will be business outcome driven by best practices and not inhibited by current conditions Outcomes will include the delivery of toolsets, services, and optimized organization structures Defined processes should be flexible enough to allow for dynamic implementation by applications Transparency and openness are essential to our group’s success. Involved parties should not be privy to punitive actions. Percent change of the ongoing cost basis and chargeback rate Percent change for the # of infrastructure-related incidents Service value defined as usage compared against cost Defined SLA’s met or exceeded Length of time to close project requests across associated tickets Survey or Rating results from HUIT partners Build the capability to configure, deploy, and operate HUIT Services in optimal ways in order to provide value for the Harvard Community The Vision for the HUIT Cloud Dev Ops workgroup Example 2: Cloud Dev Ops Workgroup Vision 14 DRAFT – FOR INTERNAL DISCUSSION PURPOSES ONLY

1.Keep it as simple as possible while still ensuring consistency and predictability 2.Deliver value incrementally and quickly to as many individuals as possible 3.Meet evolving University needs through continuous improvement 4.Promote collaboration within and between all groups 5.Support multiple methodologies and development patterns ObjectivesGuiding PrinciplesKey Performance Indicators Enable HUIT to efficiently and consistently manage IT projects that deliver value to the University through a simple and clear framework The Vision for Project Delivery Example 3: Project Delivery Framework Vision 1.Project - Define a standard framework (people, process and tools) for delivering value and transparency to the University from IT projects and programs of all sizes 2.Portfolio - Provide the ability to manage collections of current and future efforts 3.Governance - Enable clear models for evaluation, prioritization, funding, approval, resource management and measurement across governing bodies 4.Engagement & Adoption - Educate, collaborate and encourage adoption across HUIT and all of our partners 1.Increase quantity and distribution of projects utilizing Framework 2.Increased sponsor satisfaction with project outcome and process 3.Increasing stakeholder satisfaction with project portfolio 4.Reduction of number of projects delayed due to resource contention 5.Increased use of the framework for preparing proposals for governing bodies 6.Employee satisfaction with framework 7.Number of staff that have attended framework training

HUIT Software Development Standardization Project Mission: –The overall mission of the HUIT Software Development Standardization Project is to simplify and standardize software development processes to make it easier to collaborate across HUIT. We are not looking for a one-size-fits-all methodology, but rather common approaches that may be used when and where appropriate. The scope of our new standards will vary; they will range from process-oriented standards meant only for HUIT development teams, such as functional testing, to tool-oriented standards available to all developers in HUIT and across the University, such as bug tracking. 16

HUIT Software Development Standardization Project Goals: –Enable people to work across group boundaries and across HUIT –Allow new people to ramp-up quickly and be productive –Free up developers from redundant administrative tasks to allow them to focus on development and innovation –Simplify interactions between developers and support (SOC, release management, Technology & Data Services) 17

1.X ObjectivesGuiding PrinciplesKey Performance Indicators X The Vision for X HUIT X - Vision 1.X

Next Steps – 10 min

Next Steps If we decided to create a website – who would like to take on creating it and/or maintaining it? What should we accomplish first? Who would like to take on what? When do you expect to be “finished”? Do we have time to group things into themes and create a tentative roadmap? 20

Thank you! 21