Q Case study reports provide valuable opportunities to reinforce class learning. It is strongly recommended that all team members read the case, discuss it as a group, and reflect upon the business implications of the issues raised in the readings. You should work with your group to create a Case Study Report which should include the following: • One major takeaway from the broad questions asked on the M4: Case Study Overview (Link will open in new tab.) page (what you learned from studying the case) • Show how you used two concepts, one from each reading assigned for this case, to analyze the case. You can locate the articles on the M4: Readings (Link will open in new tab.) page. • Sharp and thoughtful responses to all of the following questions: o Why would developers contribute to open source? o Are open source products licensed? If yes, explain some of the restrictions licenses enforce on the use of open source products. o How can you make money with open source products? o How does open innovation differ from traditional proprietary models? When should you choose open versus proprietary innovation? Is one always better than the other? o How is MakerBot a platform business? o What is MakerBot's customer value proposition? What do you think about the pricing strategy of MakerBot? Are do-it-yourself users a big enough market for crowdsourcing? o What are the advantages and risks of open source to MakerBot? Should they stay open or become closed? o Provide some metrics and their justifications to measure the growth of MakerBot at different phases. • Member names clearly listed on the first page

View Related Questions