Learning Diary 2

Summary

Resources in project management include people, materials, tools, and infrastructure necessary to complete a project. Managing resources involves allocation, estimation, and financial planning. Effective allocation considers competence, availability, and project priorities. Estimation methods like top-down, bottom-up, and expert judgment help in planning resources and costs. A key challenge is to ensure optimal resource usage within time and financial limits.

A project schedule defines when tasks should be completed and how they depend on each other. Methods like CPA and PERT charts help visualize dependencies and decide based on that. Scheduling involves estimating task duration, setting buffer times for uncertainties, and continuously monitoring progress. Iterative schedules are used in agile projects by dividing work into smaller cycles. Tools like Gantt charts support scheduling.


Reflection

At my previous job at TaraabarNet, we used a milestone-based approach for development. Before each milestone, the product team planned the next phase, and managers of each team worked with the scrum master to estimate the workload. We used a method where tasks were given time estimates in steps of 2, 4, 8, 16, 32 hours, and we always included buffer time for unexpected issues. Developers gave their own time estimates for tasks, and these were used for planning. This relates with the bottom-up estimation method.

Even though this approach worked well, we sometimes faced unexpected problems like critical bugs or system overloads, which caused delays. This shows how important it is to have flexibility in scheduling and to prepare for risks. If I were to improve this process, I would suggest using CPA to better identify key tasks that could affect the milestone deadlines.

Comments

Post a Comment

Popular posts from this blog

Learning Diary 1

Summary A project is a temporary and unique task that aims to create a deliverable, such as a product, service, or result. It is limited by time, resources, and goals, which together form the project triangle. Good project management helps organize and control the work to achieve these goals. It includes planning, checking progress, and managing changes. Success of a project depends on good decisions, clear reporting, and meeting stakeholder expectations. The project manual helps teams follow best practices to achieve high- quality results. S cope management defines what is included in the project and what is not. The Work Breakdown Structure (WBS) helps divide the project into smaller work packages (WPs), which mak es planning and resource allocation easier. Clear deliverables are needed to track progress. A well-organized project plan should cover tasks, schedule, resources, and quality control to keep things on track.   Reflection Thinking about my own experiences, I see h...
Read more

Learning Diary 3

Summary A project organization is temporary and formed to achieve specific goals. It includes roles such as the Steering Group (SG) for decision-making, the Project Manager (PM) for planning and leading, and the Project Group (PG) that carries out tasks. Communication, delegation, and team spirit are key factors in project work . I also learned about matrix organizations and how responsibilities are divided. R isk analysis and management includes identifying , assessing, and controlling risks. Risks are prioritized based on probability and impact, and managed through strategies like avoiding, accepting, or shar ing them. A good risk management plan helps predict problems and improve project success. Reflection At my previous job, I worked on developing a recommender system. At first, our team was small, and we didn’t have a product manager. The CTO was managing the project, but he was also busy with many other tasks. Because of this, important roles like testing and risk managemen...
Read more