Sometimes I use this blog to reflect upon things I’ve learned about. One of the best ways I process information, especially information new to me is by summarizing what I’ve learned. This is why at the bottom of this document, you will see links to resources I used to write this.
One of the things I like about my new position is the feeling I have about being part of something innovative. I was lucky enough to move my stuff into my office the day before I officially started. People all around were in the process of transitioning. Some were transitioning to retirement, others were transitioning to a new position outside the department or building; and then there were those like me who were transitioning to a new position within this organization. There were boxes everywhere along with pieces of furniture in the process of being transported from one space to another. That afternoon, I got my space set up to be functional, and then wrapped things up for the day.
Walking in the following Monday morning, I felt as if I was in a completely new environment from the one I walked out of the Thursday before. Furniture was arranged in a collaborative fashion and the space was minimally, but tastefully decorated. What stood out to me the most, though was a sign on a small conference room which read “Scrum Room”. Scrum room? That sounded like a locker room for a rugby team. I didn’t think much else about it as I had a full schedule of activities for my first official day.
The next day, however, the word “Scrum” would have a whole new meaning. Our director had pushed out a series of Lynda.com videos. The first one was entitled: “Agile at Work: Building Your Agile Team”. There were also two other videos regarding the Agile framework we were asked to watch in preparation for a departmental retreat the following week. According to the videos and some side research I performed, Agile is a framework with roots in the software industry, developed for the purpose of streamlining the software development process to expedite the delivery process of a high quality product to the customer. The Agile philosophy, however, is not necessarily exclusive to the software industry. The terms collaboration, self organization, and accountability are noted as best practices of those practicing Agile. Scrum and Scrum Master were brought up regularly in the introduction and discussion of this framework.
Scrum is basically a process which insures the most valuable components of a project get completed in a reasonable amount of time. Scrum also employs the best practices of Agile to assist in the completion of these projects. From a leadership perspective, the facilitator of this process, or the Scrum Master may serve as an administrator, coach or trainer. Most importantly, the Scrum Master works to facilitate the process by pulling together the right people needed to complete the project; and then eliminates any obstacles or distractions in the way of completing the task at hand.
What makes me excited about this whole process is when I research them they are not synonymous with the field of education; which makes this innovative and exciting all at once. What’s exciting to me is that I get to be part of it!!! Interestingly enough, I have found a correlation to the Scrum process in a change model I’m getting ready to share with students this week known as the ADKAR model. ADKAR is basically an acronym facilitating the change process:
- AWARENESS for change
- DESIRE to support change
- KNOWLEDGE of how and what to change
- ABILITY to implement the change on a daily basis, and
- REINFORCEMENT to keep the change in place.
Through this model, Scrum are part of the Action and Reinforcement stages. This is exciting to me because so often there are many obstacles which exist in the field of education. The leadership in this department has a strong desire to make a sustainable change, has the ability to implement those changes and the tools needed to keep that change in place, and I can’t wait to see how all of this unfolds!
Links to Resources: