1. Release 2 Classroom Session – Day 5
October 21, 2016

2. Day 5 – Preview of Release 3 and Demo Day
Day 5 Agenda
Day 5 – Preview of Release 3 and Demo Day
Morning
Release 3: How Do You Buy? Introduction
Introduction to the Lean Canvas
Lunch (12:00-1:00 pm)
Afternoon
Live Digital Assignment Product Vision Presentations
Final wrap-up and feedback gathering
Facilitator: Glen
Duration: 10 minutes
Timing: 8:00-8:10 am
Facilitator Notes :
Welcome everyone back. It has been an long week, but a productive one.
Let’s finish strong!
Begin with telling the cohort that today we will dive in a preview of Release 3. This is in an effort to talk about what they are going to learn about over the next month and the expectations for what will be accomplished moving forward.
Then explain that the USDS team will introduce the Lean Canvas, and how it will be used to illustrate how the cohort might use it in Release 3.
After lunch, it is presentation time. Each group will get the chance to present their product vision, share their process for developing it and conducting market research, and share any lessons learned along the way. The teams can also field questions from other teams and discuss their learning experiences.

3. Review of Release 3: How Do You Buy? Key Concepts
Making the Buy
Iteration 3.A: Developing an Acquisition Strategy
Development of a strategy that buys the result, not compliance
Integrate innovative techniques to completing market research and developing your strategy
Iteration 3.B: Acquiring Digital Services
Develop your SOW/PWS/SOO
Complete your solicitation package
Ensure your evaluation criteria is complete
Facilitator: Glen
Duration: 10 minutes
Timing: 8:10-8:20 am
Facilitator Notes :
Here you want to show them how the release comes together, both A and B combined.
Release 3 is all about How you Buy now that you have completed the market research. This is where the rubber meets the road, i.e. competing the requirement. In this release, they will focus on effectively using techniques for acquiring digital service solutions in their solicitation or acquisition strategy.
Talk through the key characteristics and concepts, and talk about how they will be provided with the tools and techniques needed to develop a SOO for their case study of MAP.
Characterized by:
Developing an Acquisition Strategy
Completing Market Research and writing your report
Develop your SOW/PWS/SOO

4. Iteration 3.A: Developing an Acquisition Strategy Performance Objectives
Develop an acquisition strategy based up on your market research, product vision, and customer needs
Be an effective change agent and collaborate with the customer and key stakeholders on development of the acquisition strategy
Develop criteria on cost and pricing, terms and conditions, security concerns (cyber), and data rights.
Devise evaluation methods and criteria to evaluate vendor maturity and ability to deliver a product that solves a given need and given the definition of success.
Facilitator: Glen
Duration: 20 minutes
Timing: 8:20-8:40 am
Facilitator Notes :
Briefly review the core objectives
We start with 3.A, Developing an Acquisition Strategy. Discuss how, with their Product Vision and Market Research, they can move in to development of the Acquisition Strategy.
Discuss how you select a strategy and what considerations might impact your strategy, which ties in to the next bullet.
Then discuss the elements of criteria on cost and pricing, terms and conditions, security concerns (cyber), and data rights, ALL elements that need to be thought through when developing the acquisition strategy and part of preparing to develop the SOO.
Discuss the importance of evaluation criteria and how making a plan now can expedite your SOO development later.
What does this all lead up to? A successful procurement that meets the needs of your customer.

5. Iteration 3.A: Developing an Acquisition Strategy
Start with a strategy that leverages flexibilities in the TechFAR, Digital Services Guidebook, and other policy requirements
Will your path forward be a Challenge, MVP, RFI?
Do you need to accomplish more market research? How about a blog!
Making key decisions on the solicitation to help speed up SOW/PWS/SOO development:
Contract type
Pricing considerations
Effective use of competition
Technical constraints
Iteration 3.A schedule: October 24 through November 4
Facilitator: Glen
Duration: 15 minutes
Timing: 8:40-8:55 am
Facilitator Notes:
So how does this translate to Digital Services?
We have talked about MVPs, Challenges, Blogs, etc., so these non-traditional vendor communication methods should play a role in your strategy.
If you are using a blog to attract non-traditional vendors, what would that look like? What would you put in your blog? These are questions that will be answered in Iteration 3.A. You will also be developing a blog, so do a little research on your own and start thinking about what you would recommend as a team blog.
Walk through the main elements to consider when getting ready to write the SOO, like contract type, method of pricing, competition use (is it a Challenge, RFP, Set-aside), etc.

6. Iteration 3.B: Acquiring Digital Services Performance Objectives
Differentiate between buying compliance and buying outcomes.
Identify the role that security plays in digital service contracts.
Develop your acquisition package for procuring digital services, including proposal and source selection methods.
Define evaluation criteria, given evaluation strategy discussed in your acquisition strategy.
Share examples of acquisition innovation.
Facilitator: Glen
Duration: 20 minutes
Timing: 8:55-9:15 am
Facilitator Notes :
Briefly review the core objectives.
The biggest thing they will do in this iteration is develop their SOO. So are they ready, did they take all the steps necessary to have what they need to write the SOO?
Go over the mental checklist of what should be complete before they write and release the SOO (Facilitator to fill this in to the notes)

7. Iteration 3.B: Acquiring Digital Services
Here is where the magic happens! Time to write your Requirements Document; i.e. the SOW, PWS, or SOO
You will learn about the typical elements in a SOW/PWS/SOO and when each is most appropriate for your procurement
We are buying outcomes, not compliance!
Source selection tips and strategies, to include clear evaluation criteria in your SOW/PWS/SOO
Iteration 3.B schedule: November 7-18
Facilitator: Glen
Duration: 15 minutes
Timing: 9:15-9:30 am
Facilitator Notes :
Here, we want to talk about the development of a requirements document SOW/PWS/SOO. we want them to be able to determine and differentiate what kind of requirements document should they write? A SOO, PWS or SOW
We recommend that all digital service procurements are performance-based but are there times when want to dictate the solution? Maybe (specifically when you're working with a digital service team who knows exactly how to write requirements and are looking for that blended team experience vs. a procurement where we want industry to tell us HOW they are going to meet their solution.
When doing a SOO, it is different than an SOW in that we are buying outcomes, not compliance. And Digital Services is a moving target, so how do you solicit for vendors in a way that they can give you innovative solutions.
Also, discuss the importance of good eval criteria and how this works even in a digital services arena.
Release 3B classroom will be at ASI HQ near the Rosslyn Metro stop in Arlington, VA.

8. Lean Acquisition Planning Canvas
Acquisition Background and Objectives
Entire block would be
Duration: 1 hour
Timing: 9:30-10:30
Presented by: Shannon
Facilitator Notes:
The following slides will give a brief overview of a lean canvas. A lean canvas is a tool you can use in acquisition planning to help you brainstorm and prioritize different aspects of acquisition. A model has been provided that outlines several questions you can ask across a variety of topics to help you determine your acquisition strategy.

9. Statement of Need Cost Trade-Offs Risks
Product Vision/Objective/ Desired outcomes
Cost
Ask the following questions:
Trade-Offs
Look at the iron triangle of schedule/cost /scope/quality
Rank these factors with relation to the importance of this acquisition.
What factors need to be included in a tradeoff discussion?
Risks
What is the greatest risk to the end user?
What is the greatest risk to the agency
What is the greatest risk to acquisition success?
How do we mitigate these risks?
Acquisition Streamlining
What does industry engagement look like?
Can you start with a blog to get interest?
How do we craft a message that makes industry want to work on this acquisition?
What does phased approach to acquisition look like?
Applicable Conditions
Is there an existing legacy system that is replacing
What cost, delivery, environmental constraints exist?
What will this have to interface with?
Is this going into a cloud environment? Why or why not?
Can you use open source? Why or why not?
Delivery or performance requirements
What can be envisioned for a minimum viable product
Do you need a design phase?
What does modular contracting opportunities look like for this?
Are there program or organizational dates that affect urgency or performance?
Timing: 3 minutes
Presented by: Traci
Facilitator Notes:
Using the lean canvas, you should ask questions regarding the statement of need, cost, trade-offs, risks, acquisition streamlining, applicable conditions, and delivery or performance requirements. Brainstorming the answers to these questions in each category will help guide your process.

10. Are there required sources or vehicles?
Test and evaluation
Ask the following questions:
What is the extent of testing that to be accomplished before production release?
How will you incorporate usability testing?
Do you have IV&V requirements or contracts?
How will automated testing be incorporated?
Sources
Are there required sources or vehicles?
Are there preferred sources or socio-economic category requirements?
What is the result of market research?
Competition
Will this be competed?
What are the competition goals?
Budgeting and Funding
How much budget is set out for this?
Is there an IGCE?
What is the office willing to invest to get to success?
What fiscal year concerns related to funding need to be addressed?
What color of money is being used?
Logistics Considerations
What is the impact or requirements for operations following a MVP deployment?
Will you include data rights clauses in your solicitation
Are you willing to develop in the open and share development with other agencies?
Contract administration
Contract Type
Acquisition Considerations
Have you considered open source, mixed source, cots, or proprietary software as referenced in the Federal Source Code Policy
Will you be using Performance based acquisition? Why or why not?
Source Selection Procedures
Have you considered a multi-phased approach to source selection?
Will you have a coding or agile walkthrough challenge?
Who is performing the technical evaluation and what is their current agile or design maturity?
Is EVM required?
What is your timeline and plan for negotiations?
Will you consider due diligence and discussions with vendors?
Timing: 3 minutes
Presented by: Traci
Facilitator Notes:
Additionally, you should ask questions regarding the test and evaluation, sources, competition, budgeting and funding, any logistics considerations, contract administration and type, acquisition considerations, and source selection procedures.

11. Live Digital Assignment – Prep Time
Facilitator: Heather Govoni
Duration: 1.5 hours
Timing: 10:30am – 12:00 pm
Notes:
Provide participants with time to prep for their live digital assignment presentations. If the preceding discussions run over, then this section can be compressed as needed.

12. LUNCH! Facilitator: Heather Duration: N/A
Timing: Lunch is scheduled to occurred from 12-1 pm. Adjust that timing depending on how the schedule is moving along.
To prepare for LDA assignment presentations after lunch, encourage participants to load up their materials to the facilitator’s computer using a jump drive and/or by ing their presentation.
Cue up presentations on facilitator computer so that presentations are ready for use after lunch.

13. Live Digital Assignment
Presentation Time
Facilitator: Heather
Section Duration: 2 hours
Timing: 1-3 pm

14. Your Presentation Instructions
Please get into your team and get your presentation materials ready.
Facilitator: Heather
Duration: 5 minutes
Timing: 1:00-1:05 pm
Facilitator Notes :
Get everyone settled and into their teams. Make sure to visit with each team and see if they have everything they need to present.
Brief the class that each team will get 10 minutes to present and at the end for their presentation, we encourage other teams to ask questions.

15. Welcome to Demo Day! Each group presents (about 10 minutes)
Cohort responds and offers insight
Share your feedback with the LDA group
Facilitator: Heather
Duration: 10 minutes
Timing: 1:05-1:15 pm
Facilitator Notes :
Brief the class that each team will get 10 minutes to present and at the end for their presentation, we encourage other teams to ask questions. For those of you in the audience, it’s your responsibility to pay attention and provide feedback to the group presenting. Ask any questions you may have, and provide insights.
Here’s a summary of what your presentations should cover, as per the 2.B assignment in the portal:
* Your overall project and hypothesis. Discuss you experiences using the design process to hone in on this hypothesis.
* Your plan for executing and testing your hypothesis. How are you planning on (or how have you been) using agile principles to test your hypothesis?
* Your product vision (i.e., the need you are addressing for your customer).
* Systems/collaboration tools that you’ll use to execute your plan.
* Your key learnings/takeaways, successes, challenges, and anticipated next steps. To craft this section, ask yourselves questions like the following: What are you most proud of? Where have you struggled most? What are you most excited about as you move forward?
* Questions for the group or challenges you’re currently working through.
You will have time after your presentation to gather feedback and advice from your classmates, and to engage in collective problem-solving. Your presentation should include at least one challenge or question that you pose to your classmates/the full group.

16. Group Order Team 1: WebExers (Coach: Brent)
Team 2: Pied Piper (Coach: Shannon)
Team 3: Stone Ponies (Coach: Shannon)
Team 4: Team US (Coach: Clair/Traci)
Team 5: Scrum n' Roses (Coach: Clair/Traci)
Team 6: Fragile Development (Coach: Brent)
Facilitator: Heather
Duration: 2 minutes
Timing: 1:15-1:17 pm
We plan to have the groups present in chronological order to make it easy!
Each team will have 10 minutes for their presentation and 5 minutes for questions.

17. So What Did You Think? After hearing the product vision:
Do you think it captures the goal for the end user?
Will it lead to the desired acquisition strategy?
Is it concise enough?
Will it serve as an accurate filter for change requests, design adjustments, etc; i.e. will it keep you on track to achieving the vision?
Facilitator: Heather
Duration: 3 minutes
Timing: 1:17-1:20 pm
Facilitator notes:
Have participants think about the questions on the slide during each presentation and remind them what a good product vision looks like.
Be clear on the difference between the product vision and the product and don’t confuse the two. The former is the motivation for developing the product; the latter is a means to achieve the overarching goal. Say that I want to create a computer game that allows children to choose and interact with characters, select different music tracks and worlds, choreograph their own dances, and play together with friends. This might be a nice idea, but it is not the actual vision. An effective product vision goes beyond the product and captures the change the product should instigate. A vision for the game would be “Help children enjoy music and dancing”.
Product vision is the prerequisite for choosing the right strategy. If you don’t have an overarching goal then you cannot decide how you best get there. This is nicely illustrated by the famous conversation between the Cheshire Cat and Alice in Alice’s Adventures in Wonderland. Asked which way Alice should take, the cat replies: “That depends a good deal on where you want to get to.” “I don’t much care where –,” says Alice. “Then it doesn’t matter which way you go,” responds the Cheshire Cat.
Use the vision to guide your product decisions and to focus everyone on the ultimate reason for creating the product. While the vision alone is certainly not enough, it is a first filter for new ideas and change requests: Anything that helps you move closer to your vision—be it a new feature, a change of direction, or a new technology— is helpful and should be considered; anything that doesn’t, is not beneficial and should probably be discarded.

18. Presentation Time! Facilitator: Heather Duration: 1.5 hours
Timing: 1:20-3:00 pm
Notes:
Reminder that each team has 5 minutes to present and 5 minutes for questions. There are 6 teams, so that comes to 60 minutes. (The extra 30 minutes is wiggle room if presentations go over.)

19. Wrap Up & Classroom Session Feedback
Facilitator Notes – Heather:
Now that you’ve had time to see all of the presentations, we wanted to come back together to debrief on the past three days and gather your feedback on your classroom experience. This will be similar to the orientation session, we’ll be closing with the “liked, learned, and longed for” post it activity.
Duration: 1 hour; this slide: 2 minutes
Timing: 3-4 pm; this slide: 3:00-3:02 pm

20. Classroom Session Review – Day 1
Live Digital Assignment working session
Facilitator Notes – Heather:
Ask participants how helpful the LDA working session was for their groups.
Duration: 5 minutes
Timing: 3:02 – 3:07

21. Classroom Session Review – Day 2
Teambuilding Activity
Brief Review of Release 1
The Importance of Understanding Stakeholder Challenges
The Importance of Understanding Stakeholder Challenges (Part II)
Live Digital Assignment Group Work
Facilitator Notes – Heather:
Ask participants what stood out to them in each piece of Day 2:
Teambuilding Activity
Brief Review of Release 1
The Importance of Understanding Stakeholder Challenges
The Importance of Understanding Stakeholder Challenges (Part II)
Live Digital Assignment Group Work
Duration: 5 minutes
Timing: 3:07 - 3:12

22. Classroom Session Review – Day 3
MAP Case Study Activity Review
Beyond the RFI
Beyond the RFI in Action Exercise
Case Study Recap
USDS Guest Speakers
Facilitator Notes – Heather:
Ask participants what stood out to them in each piece of Day 3:
MAP Case Study Activity Review
Beyond the RFI
Beyond the RFI in Action Exercise
Case Study Recap
USDS Guest Speakers
Duration: 5 minutes
Timing: 3:12-3:17 pm

23. Classroom Session Review – Day 4
Salesforce Market Research Study review
Influencing Conversations Roleplay
Transitioning from Market Research to Discussion of Acquisition Strategy: VA Guest Panel
Facilitator Notes – Heather:
Ask participants what stood out to them in each piece of Day 4:
Salesforce Market Research Study review
Influencing Conversations Roleplay
Transitioning from Market Research to Discussion of Acquisition Strategy: VA Guest Panel
Duration: 5 minutes
Timing: 3:17-3:22 pm

24. Classroom Session Review – Day 5
Release 3 Introduction to the Acquisition Strategy
Lean Canvas introduction
LDA Report Out and Reflection
Facilitator Notes – Heather:
Ask participants what stood out to them in each piece of Day 5:
Release 3 Introduction to the Acquisition Strategy
Lean Canvas introduction
LDA Report Out and Reflection
Duration: 5 minutes
Timing: 3:22-3:27 pm

25. Liked, Learned, Lacked, Longed for Feedback on Orientation
Liked – things you really liked
Learned – things you have learned
Lacked – things you have seen the team doing, but consider that could be done better.
Longed for – something you desired or wished for
Facilitator Notes:
Review what’s on the slide, then:
On the _ sticky notes, write your liked comment.
On the _ sticky notes, write your learned comment.
On the _ sticky notes, write your lacked comment.
On the _ sticky notes, write your longed for comment.
Duration: 33 minutes
Timing: 3:27-4:00 pm