Learning Journal

Student Name: Yatish Chutani

Course: SOEN 6841

Journal URL: https://github.com/YatishChutani/SOEN6841-SPM/wiki

Week 1: Jan 18 – Jan 24

Date: Jan 22

Key Concepts Learned: The two main topics covered this week included the overview of the tasks involved software project management and development and software project initiation. The first topic explained the processes involved in a software project, the role a project manager plays, the integration and allocation of resources in the development, and some of the management metrics which define the quality characteristics of the project. The second topic highlighted the key tasks involved when a project is initiated, a project charter and the planned tasks and objectives of the project. In addition to these topics, we also discussed case study relation to a real time project development.

Application in Real Projects: This week’s learnings shed light on the basic concepts involved in software project management that are necessary for developing a project. As discussed in the class, the case study that we read portrayed the implementation of these concepts on a real-time problem which was tackled as we studied more about it. Moving forward, the key point that I felt was important was the uniformity of changes that took place as we moved from the current to the updated build. Learning taught in the further classes will provide a better picture on the subsequent steps involved in the project development.

Peer Interactions: There was one interaction with the peers in the classroom when the discussion related to the groups for posterathon and project was taking place. I did form a pair for posterathon with whom I initially discussed the topic for poster. As the groups were also formed, I dropped a text on moodle to the group members for in interaction session.

Challenges Faced: The concepts taught this week were basics in software project management. So, there were no such challenges encountered while studying. The topic project charter needed a little more explanation so I surfed on the internet and read more about it which cleared a few points that I had in mind.

Personal development activities: This week I performed several coding tests and took part in Hackathon for my professional development. These will help me practice coding and ace the interviews that I will give in future.

Goals for the Next Week: The main goal for next week is reading chapters 3, 4 and 5. I will also read more about the project initiation steps that were involved in development and implementation stages as discussed in chapter 2. Any difficulties or challenges faced in the upcoming chapters will also be solved in the coming week.

Week 2: Feb 04 – Feb 10

Date: Feb 09

Key Concepts Learned: The key concepts learned this week talked about the meaning of effort estimate of a project and also the techniques used for effort estimation. The other concept we learned was the cost estimation as well as about the cost estimation techniques. Other topics like schedule estimation and resource estimation were also taught which, at the end, highlighted the different estimations that are related to a project which play a crucial role in the project planning stages and derives the course of action that needs to be followed.

Reflections on Case Study/course work: This week’s learning like Function Points Count Analysis is used to estimate software development effort and cost based on the functionality provided by the user. Another topic, Critical Path method, which is used to identify the longest path of dependent tasks to determine the project duration. We learned many similar concepts that have application in real life project and are used in software project management in the planning phase.

Collaborative Learning: The group discussion for the project took place where I met 3 group members. Our meeting’s main aim was to discuss about the project topic and talk about the thoughts and opinions on the project. We also assigned tasks that each member has to complete before the next meeting which is supposed to happen next week. In all, it was a very productive week where a lot of discussion took place.

Further Research/Readings: This week's lessons covered the fundamentals of different estimations and their techniques in software project management. Thus, no such difficulties arose during the course of the investigation. The topic PERT(Program Evaluation and Review Technique) needed a little more clarification, so I looked it up online and read more, which answered some of my questions.

Adjustment to Goals: This week I performed several coding tests and staring an online course for preparing for Data Structures which will help me in preparing for my interviews. I also joined the gym for engaging myself in some physical activities for the overall development.

Week 3: Feb 04 – Feb 10

Date: Feb 09

Key Concepts Learned: This week's most important lessons included learning what exactly a risk in a project is, recognizing the different kinds of risks that could occur, appreciating the possible effects these risks could have, and developing suitable plans to effectively manage and reduce them. Technical, environmental, financial, and organizational issues are only a few of the many variables that can compromise project goals and are considered risks. Project managers can guarantee project success despite uncertainties by anticipating possible problems, evaluating their likelihood and severity, and putting mitigation plans into action. We also learned about the strategies that are required to deal with the potential risks and getting a better result in the future.

Reflections on Case Study/course work: The case study presented in Chapter 4 offers insightful information on risk management in a software development project that a SaaS vendor is involved in. The concerns that were discovered included a wide range of topics, including the feasibility of offshore teams, attrition, communication gaps, development expenses, timetable adherence, and software quality. Several techniques were put into place by the development team to reduce these hazards. They used virtual meetings, standardized communication techniques, and kept extra time in the project timeline. They also set features in order of importance during iterations to guarantee that, even in the face of unforeseen difficulties, crucial activities were finished on schedule. When necessary, overtime was approved to make up for a lack of resources, and thorough quality assurance procedures were incorporated into the development process. In order to ensure project success in the face of uncertainty, this case study highlights the significance of proactive risk identification and reduction.

Collaborative Learning: Participating in group activities and cooperative experiences has greatly improved my comprehension of a number of subjects this week. Collaborating with colleagues offered a range of viewpoints and understandings, promoting a deeper understanding about the aspects of risk management. Through collaborative problem-solving, brainstorming sessions, and group discussions, I was exposed to a variety of methods and techniques. Working with peers pushed me to actively listen and be open to different points of view in addition to allowing me to share my views. We booked group study rooms in library this week to discuss about the project as well as about the learnings of the week and how these learnings can be incorporated into our project. All in all, the group project discussion I worked on this week improved my learning process by encouraging cooperation, effective communication, and peer support.

Further Research/Readings: This week, I also looked at case studies on risk management in project management literature and read articles about virtual teams' successful communication techniques. These resources enhanced the course content by offering practical illustrations of risk identification, evaluation, and mitigation in project environments. The case studies provided useful information that could be used to our talks on risk management techniques by providing real-world insights into the difficulties faced by software management teams and how they solved them. The papers on virtual team communication tactics also improved our knowledge of how to lessen the dangers brought on by distance, time zone variations, and cultural diversity. I also went on the internet reading blogs related to the times when big software teams had problems while working on projects and how they overcame these risks after proper evaluation of the risks.

Adjustments to Goals: After going over the objectives for the previous week, I set out to study chapters 4 and 5, have a deeper comprehension of the project's subject, and finish a job that would be discussed at the project meeting. When I look back on my development, I can say that I studied the chapters with success and learned about project risks and strategies. I am aware, yet, that more study is necessary to improve my comprehension of the project's subject. Even though I completed the assignment given to me, I recognize that it still needs to be improved to meet standards. Changes include giving research additional time, asking questions about topics that aren't quite apparent, and improving the work that was given based on input from others. These modifications are intended to guarantee thorough learning and efficient task fulfillment.