Curriculum Innovation or Confusion

Share This Post

It is an early Monday morning just prior to the beginning of the semester.  A faculty member walks into the institution where he teaches.  He will be working on a curriculum project. He thinks through the steps to be completed.

  • 50% of the content be new or requiring modification
  • Curriculum Contract
  • Selected Modality
  • Credit for Prior Learning (CPL) exam
  • Guideline/Documentation Checklist
  • Curriculum Repository
  • Learning Management System
  • Peer Review
  • Approval 

The aforementioned checklist has multiple sub steps. Your institution may have a different process. I would bet, though, that your process has encumbrances that hinder your ability to provide current curriculum in a timely and cost-effective manner. If you were to flowchart the steps, would it look simple and easy or more like a Rorschach test?

The largest hurdle might simply be the speed at which knowledge advances. Consider the simple act of information exchange. If the amount of information exchanged electronically were converted to newspapers, each individual would receive approximately 55 newspapers in 1986 and 175 in 2007 (Hilbert, 2012).

I encourage you to do some reflection. Is your institutional processes a hindrance? What changes can be made to make you more effective as a faculty member/department? How often are you able to make changes? Are you using the waterfall-like ADDIE (Analysis, Design, Development, Implementation, and Evaluation) process? I would encourage you to look to Agile methodologies to improve the process – make it more efficient, less costly and more enjoyable.



Hilbert, M. (2012). How much information is there in the “information society”? Significance, 9(4), 8-12. doi:10.1111/j.1740-9713.2012.00584.x

More To Explore


Demystifying Scrum User Stories Confirmation: Ensuring Quality and Collaboration

One of the key elements of Scrum is the use of user stories to define the requirements of a system or feature from the perspective of the end user. As teams work through the product backlog, it becomes crucial to confirm the user stories to ensure they meet the desired criteria and are ready for development. In this blog post, we’ll explore the concept of Scrum user stories confirmation and its significance in delivering high-quality products.


The Power of Conversations in Scrum User Stories

At the heart of Scrum lies the concept of user stories, which serve as a means of capturing requirements from the perspective of end-users. However, the true power of user stories lies not just in their written form but also in the conversations that take place around them. In this blog post, we will explore the significance of conversations in Scrum user stories and how they contribute to the success of Agile projects.

Do You Want To Boost Your Business?

drop us a line and keep in touch

Scroll to Top

Need help?

Let's have a chat...


Jump Back In!

Here at Webolution Designs, we love to learn. This includes sharing things we have learned with you. 


Begin Your Learning Journey Today!

Come back inside to continue your learning journey.