Approaches to Inquiry Response

I really liked the ‘Seeking Revenge in the Underworld of Stolen Bikes’ story. I was just talking with a friend the other day about how rampant bike theft is; several of our friends have had their bikes stolen in the last few years. I certainly think this represents what I think of as inquiry. The main character starts with a desire to know more about bike theft and follows his curiosity to a variety of places, learning a lot along the way.

Through talking in class about the differences between traditional research papers and the inquiry project you would like us to complete in this course, I have drawn a few connections to another course in which I’m currently enrolled, ITIS 3300 Software Requirements and Project Management. The connection is that traditional research papers are to inquiry papers as traditional project management is to agile project methodology. The connection became clear when you put up the flowchart diagrams representing the research and inquiry paper-writing processes. In traditional waterfall projects, the project manager and stakeholders clearly define how the end result is supposed to look and follow a strict step-by-step process: plan -> design -> build -> test -> correct -> test -> deploy. Once one goes from one step to the next, one doesn’t go back. With agile, the project manager and stakeholders have an idea of what they want and then begin an iterative process focusing on getting one or two small chunks of the whole prototyped and then return to the stakeholders and confirm it’s what they want or pivot according to new insights. In this way, much like with the inquiry process, there is much more freedom to change direction and follow one’s curiosity and end up with a product truer to the real business’s needs and wants with the agile project management methodology.

Word Count: 308