This week I
feel like we got a lot accomplished as a group. The Charter was completed and a
Google Doc was created so that all members could contribute. We also met three
times this week (on Sunday, Monday and Wednesday) and communicated on a daily
basis. We also began to compile a list
of potential volunteers for lesson plans. I updated an invitation email and we will
have completed a second invitation by Sunday to send out to teachers
implementing MTVT.
I also spent
a lot of time re-reading and researching project charters. I found myself
referencing the Project Managing E-Learning book numerous times. I also was looking for a user-friendly WBS
tool to utilize. Having the resource
sharing in Google communities was a real benefit. As a group we selected the template provided
by Daniel.
Although still overwhelmed by the project as a whole, creating the
charter really gave me a solid understanding of the overall project. Writing the charter broke the process down
and provided a greater understanding of the needs and expectations. The purpose of the charter is to
create a preliminary delineation of roles and responsibilities, outline the project
objectives, identify the main stakeholders, and define the authority of the project
manager. It serves as a reference of authority for the future of the project.
The charter provided the group a clear sense of direction.
The Work Breakdown Structure represents all
the work required to complete this project. The general overview seems manageable
but when I think of all the steps broken down this will be a challenge.
Team members have been communicating on a daily basis either
through phone, texts, email, or in our community. Each day we are working
through that material. Having the opportunity to meet with Dr. Mims as a group
was extremely valuable and we were able to develop the scope of our project. We
also have a solid understanding of what our clients needs are. We have already begun
gather and reviewing information.
I created a Gliffy graphic flow chart as a visual break down of
the project that simplified a starting point for our research. It’s a simple version
of the WBS it was just a general overview for me to use as a starting point. Rather
than becoming overwhelmed this simple flow chart provided a broad overview of
what we need to accomplish.
Creating a
flow chart is a step up form my typical checklist. The flow chart allows me to visualize one step
and then the next. The flow chart will be elaborated on with our Gantt
scheduling tool. It will be more detailed and broken down. I also believe that the Gantt tool will not
only serve as a great scheduling tool, it will also be a method to document our
hours.
Based on our
WBS, the stats are mapped out on our next task during which we will be creating
the needs analysis. We all need to start documenting in Ganett. I believe this tool will serve as a great
organizational and time management tool. So far I feel like every day some type of task
is due. In order to be productive you need to be working on this project
everyday. I think if you step away you
will constantly be trying to play catch up with the amount of work required for
this project.
Having set
meeting times is efficient. Posting in the Google community allows for continuous
communication and also allows for collaborations.
The
next plan of action is to continue researching tech tools, lesson plan templates,
tutorials and various strategies used to incorporate the tutorial visuals. The
analysis report is due next week. Having
a student’s prior project as a reference example is extremely valuable. Reading
it in a book is certainly different than seeing a real world end product.
-
5
hours project charter/research
o
Submit
for approval
-
5
hours Team Meeting Google +
o
WBS/Charter/Tasks/To Do/
-
1
hour MTVT invitation Email/Google Doc
-
2
Gliffy Chart
-
1
Hour WBS template/research
Next
Week: Analysis/Reading/ Research
No comments:
Post a Comment