Projects
Daily Log
Project Feedback
| Situation | Behavior | Impact | Is it in line with expectations? | Action Plan to address this | Learnings and Adjustments |
|---|---|---|---|---|---|
| Wanted to do a POC and was asked to timebox it to 3 days and keep updating on the progress | Switched directions from POC to a spec. Never informed manager or his mentor | Expectations were not met. We were expecting a POC and we didn’t see a poc or a completed spec at the end.We also couldn’t reset expectations | No | Needs to work on timely communication and sharing important information | Following feedback, I took some time for self-reflection and initiated a retrospective with team members. I've formulated a plan to implement their feedback and ensure that I meet expectations moving forward: Refined Approach: - Scope Communication: I will keep stakeholders informed whenever the project scope expands, specifying the additional effort each new change introduces. - Consider shadowing an experienced team member? - Schedule a discussion to clarify details. - Change Evaluation: I'll collaboratively assess the value of each proposed change and strive to understand its contribution towards our final objectives. For instance, understanding the team’s evaluation on current key performance indicators clarified the importance of certain features. - MVP Focus: I will clearly outline the essential components necessary for the most basic version of the product. This ensures we maintain focus on critical metrics while testing our hypothesis and moving swiftly to further enhancements. I will engage in constructive discussions to creatively address the scope of any additional features, aiming to reduce development time. - Efficient Communication: If a messaging thread becomes lengthy or a specification requires extensive time to finalize, I will arrange a quick sync with stakeholders to ensure alignment. - Kickoff Meeting: Include project manager, directly responsible individual, other engineers, and business-to-business contacts as necessary. - Sizing: Organize a quick call with engineers, especially those familiar with the relevant codebase, to achieve a consensus on effort estimation. - Managing Frequent Spec Changes: - Create an outline. - Review in a synchronization meeting. - Convene when changing strategies. Progress on Improving this Skill: • Flexibility: When a team member identified a more efficient strategy, I quickly recognized the benefits of shifting our focus to this new approach, facilitating a discussion to refine it. This pivot streamlined our process, potentially halving the execution time. • Proactive Meeting Scheduling: When discussions about new strategies expanded beyond brief messages, I followed through with advice to organize a one-on-one meeting, which resolved many uncertainties and resulted in a concrete action plan. • Streamlined Communication: Acting on a suggestion, I prepared a concise summary and segmented the content to involve only relevant stakeholders, reducing the time needed for comprehension. • Simplifying Metrics Strategy: Building on feedback, I led the conversation to simplify our approach to metrics, emphasizing the benefits of a streamlined strategy. We reached a consensus on this approach, saving significant time and effort. • Prompt Scope Notification: In response to feedback, I quickly updated the team about any changes to their scope of work, ensuring everyone was informed and aligned. |
Velocity Tracking
Draft Spreadsheet Template