MIS 3535 Journal Entries
Week 1: February 6th
The week ending on February 6th, the PM’s worked on various tasks such as the risk management plan, communications plan, quality management plan and change management plan. Communication with the BA’s has been inconsistent because they cancelled the meeting we set up on Wednesday at noon. Prior to that it was going well because we met with them the week before and discussed project details and the scope document as well helping them prepare questions for the first interview. Hopefully the next week we can meet with the BA’s to set up a weekly meeting time.
Week 2: February 13th
This week the PM’s worked on our work breakdown schedule and figuring out our budget. The team met with the BA’s twice this week, the first meeting we discussed the team scope document and helped them edit their paragraphs. We then met up with the BA’s before their second interview and assisted them with some questions. We set up a meeting to happen every Wednesday from 1:30-3:00. We then helped the BA’s study for their exam by telling them key areas to study.
Week 3: February 20th
This week the PM’s worked on figuring out which deliverables each team member would tackle. The BA’s took their first exam and said it was challenging. Also, the BA’s team scope document was due on Thursday February 19th, we spoke with various BA’s about how they felt about the scope and they felt confident it was their very best work. The PM’s edited the scope document in the google drive we set up to make sure it was error free and within the scope of the project.
Week 4: February 27th
The project managers met with some of the BA’s to get a better understanding of their progress with the deliverable’s. The team seems to be a little behind schedule and that is partially our fault for not increasing urgency and instilling fear. Cassandra created a Doodle so we could narrow down a time for our weekly meetings where all the BA’s could meet and most of the PM’s. We also helped with interview 3 questions and sat through the interview. The team did a below average job of asking open ended questions and to get the speaker to elaborate. The PM’s let the BA’s know of their mistakes and how to remedy the situation by asking some relevant follow up questions.
Week 5: March 13th
Week 5 has been our best week yet in terms of communication and overall progress with the BA’s. The team met on Wednesday and got a better understanding of how the deliverables were coming along. Some of the BA’s started working on JIT which was good to see. Meanwhile the PM’s created the RACI chart to organize duties, we also created a list of stakeholders and an organization chart. The weekly meeting time has been established and hopefully does not change.
Week 6: March 20th
Week 6 was a slow week in terms of progress with the BA’s because they were busy working on studying for the second exam. They asked us questions about focus areas to study, for example what types of case studies were going to be good to study from. They worked on JIM prototyping ideas after the exam, we helped them by giving advice from what worked with our prototype and what didn’t.
Week 7: March 27th
Week 7 the PM’s met with the BA’s to get an update on project deliverables. The prototyping is coming along well and the team has good ideas on how to improve the final product. They were stuck on how to do some things in JIM so we showed them some tips. They have done a good job allocating tasks to different members of the group so people with different strengths shine in what they do best. The Pm’s worked on learning how to create the critical path and EVM.
Week 8: April 3rd
This week the PM’s met with the BA’s to get a project update on requirements and prototyping. The prototyping is coming along on time, some of their ideas are very innovative and new. The BA’s on completing deliverables on time and now we have to keep them motivated to finish the project strong. The PM’s worked with the BA’s on JIM and helped them with idea’s for final prototype.
Week 9: April 10th
During week 9 the PM’s worked closely with the BA’s on delivarbles and prototyping. The BA’s have been working well together and group work has not slowed down at all. The prototype is coming along well and we helped them with a few ideas they can implement into their prototype. The PM’s worked on the updated risk management plan and determined some of the techniques we will use to manage the risks of the project.
Week 10: April 17th
During week 10 the PM’s met with the BA’s to discuss the final prototype and presentation. The prototype is almost finished and has some very good features but we suggested a couple more to them. On the other hand, the deliverables need some work and we will assist them in completion of those. The PM’s did alot of work this week from change management, risk management plans, we are starting to put together a rough copy of our final binder.
Week 11: April 24th
This was the last week of the project and everything was coming full swing. Prototype was finished and the team did a great job presenting their business case to the client. They did an excellent job with the follow up questions thrown at them too. The PM’s worked on getting the final binder ready and deciding which deliverables to include and what to not include.