Setting Up Project Management Workflows

Do you feel anxiety when looking at your Product backlog with those 1014 tickets? What if I told you there is another way? Here are 8 ways to keep your backlog clean and actionable: 1) Differentiate between a backlog item and an idea - It's ok to have a notebook, Figma, mural, whatever, where you collect all ideas and requests. However, the backlog should only contain items you aim to work on FOR REAL within the next 1-3 quarters. 2) Set a hard limit of tickets - In my experience, only the top 20-30 tickets will actually have any chance to ever be closed as completed. There are too many new directions, opportunities, and urgent tasks coming in overriding the priority of tasks further in the backlog. Just close the items that will never happen or at least move them to your ideas space. 3) Don't make it a BUGlog - bugs are tasks like all others. They need value and effort estimation and have to be prioritized against any other product opportunity. If they don't make the cut, they don't make the cut, sorry. No point collecting bugs - they are not Pokemon! 4) Keep the tickets high quality - However, if there is something in your backlog, let it shine! Make sure to include the user story, impact hypothesis, requirements, and links to design and tracking specifications. The tickets should be able to speak for you when you are not around. 5) Try to have 3 months' worth of refined items ready to go - It might be hard (try daily refinements!) to achieve and it's worth it! With items ready for the next 3 months for the team can pick up, you will have so much time to do proper long-term planning and assessment. It's worth the initial effort! 6) Introduce visual cues - It's much easier to look at the backlog if you can easily tell apart a new feature task, improvement initiatives, bugs, and research. If you add other color cues to represent item status, you will be able to tell everything at a glance. 7) Add key stakeholders to their tickets of interest - A personal update email may work. Automated status updates work too and keep relevant people in the loop with no time investment on your end! 8) Create a task document associated with a backlog item - This is basically an extended version of the ticket, where you can collect all the pre-development research and post-development results and observations. Collecting this info in one place saves you hours when it comes to writing progress updates and presentations. At the same time, your tickets remain clean and hold only the relevant information. There you go! Here are my 8 ways to keep the backlog neat and functional. Will those work for your backlog and if not, why? Or perhaps you can contribute more pieces of advice? Sound off in the comments! #productmanagment #productmanagers #backlog P.S. Having a clean backlog is one thing. Having great tasks to put there is another challenge. To be well equipped to face that challenge, check out my courses at drtbartpm. com :)

As a creative who specializes in photography filmmaking, I usually receive emails and messages from creatives seeking advice. Over the years, I’ve written down and reminded myself of certain key points with each project. I thought it would be beneficial to share some of these ideas here on LinkedIn. 1. Debrief: After each project, taking the time to debrief is essential. Reflect on what you did to achieve the goals, identify the challenges faced, and consider how you and your team can learn from the experience. Evaluate whether your ideas were too ambitious or if the brand or client didn’t fully connect with your vision. Gathering all this information helps you refine your approach and apply these lessons to your next project, guaranteeing continuous growth and improvement. 2. Clear Communication: Establishing open and transparent communication from the start ensures that everyone is on the same page, from the production team to the client. This helps manage expectations and keeps the project moving smoothly. 3. Collaboration: Successful projects are built on collaboration. Engaging with your team, valuing their input, and working together towards a shared vision is key to creating something special. 4. Adaptability: Flexibility is crucial in creative work. Whether it’s adjusting to last-minute changes or finding creative solutions on the fly, being adaptable keeps the project on track. Remember to be Nimble! 5. Storytelling: At the core of every project is a story. Whether it’s a photo shoot or a film, the ability to tell a compelling story that resonates with the audience is what sets the work apart. Story is everything. 6. Attention to Detail: The little things matter. Paying close attention to every element—from lighting and composition to styling and post-production—elevates the final outcome. It's all in the details. 7. Client Relationships: Building and maintaining strong relationships with clients is just as important as the creative work itself. Understanding their needs, keeping them involved, and delivering on promises fosters trust and long-term partnerships. Remember no client is the same. 8. Passion and Purpose: Bringing your passion and sense of purpose to every project keeps the work authentic and impactful. It’s not just about the final product, but the process and the message behind it. This is your personal stamp and DNA don't forget it. 9. Professionalism: From meeting deadlines to maintaining a positive attitude, professionalism sets the tone for the entire project and ensures a smooth experience for everyone involved.

I generated 25+ campaign ideas for my client without using AI. Here’s my 6-step creative ideation process: ➡️ Step 1: Understand the End Goal Before anything else, you should understand the overarching marketing and business objectives. Ask yourself the following: Who do I want to reach? Why? What impact do I want to have? What would success look like? ➡️Step 2: Discovery & Research To think strategically down the line, use this step to gather info: 📊 Internal content audit → Examine what’s been done so far and look in depth at what has and hasn’t worked (and why) 🔍 Competitor analysis → Dive into your competitors campaigns, their effectiveness, and how people are reacting to them ➡️ Step 3: Empathise Get to the root of your target audience’s needs so that you can address their pain points. This means you can show how your product/ service solves a problem they’re facing. (Ex - A personal branding agency recognising that their ideal client struggles with lead gen. They use social proof to demonstrate how they’ve successfully created content that positions their current clients as industry leaders). ➡️ Step 4: Inspire Creativity Through Brainstorming Creative thinking is all about experimentation, imagination and curiosity. Let your mind run free here and allow yourself to spontaneously brainstorm. Quantity > quality is best at this stage. Some examples of brainstorming techniques: 💭 Create a mindmap, drawing branches from each idea 💭 Reframe and reword your target audience’s problem, looking at it from different angles 💭 Think outside the box i.e. ask ‘how would a child solve this problem?’ 💭 Test the waters of constraints and aim to brainstorm 10 rough ideas in 10 mins ➡️ Step 5: Relax & Unwind Giving yourself breathing space after so much thinking. It can stimulate subconscious ideas. ⛅️ Walking 💭 Meditating 🚿 Taking a shower 🎶 Listening to music It’s often in these moments that we connect unexpected dots and ‘lightbulb moments’ are triggered. ➡️Step 6: Unlock Your Creativity It’s solution time! Having completed steps 1-5, you’re now ready to generate innovative ideas to test. Evaluate and select the ideas you think will have the greatest impact. At this step, you want to whittle the best ideas down so it’s quality > quantity Quick idea generation checklist ✔️ 1. Understand what you want to achieve and why 2. Research internal content & your competition 3. Put yourself in the shoes of your ideal target audience 4. Get inspired through brainstorming techniques 5. Schedule downtime and give your mind a rest 6. Generate, evaluate and select ideas P.s. don’t just take my word for it that all of this planning & prep is worth it. Take Einstein’s advice: “If I had an hour to solve a problem, I’d spend 55 minutes thinking about the problem and five minutes thinking about solutions.” What helps your creativity when it comes to ideation? 💡

Tired of arguing with your coworkers during #codereviews? Why not start a Team Working Agreement with your #softwaredevelopment team? A team working agreement sets the ground rules for your team and how they review code. You should discuss and document key things like: 1. How fast should reviews happen? Agree on an appropriate turnaround times for reviews and state that in your TWA. Also describe what can be done if someone isn't adhering to the turnaround times. 2. What's our limit on PRs? Define PR size limits: whether that's roughly the amount of lines changed or a maximum on the number of files to be reviewed, a guideline can help keep a #pullrequest small. And remember: Small PRs mean faster, more efficient reviews. 3. Are you allowed to self-approve? Handle self-approvals: Can authors approve their own PRs? If so, when and under what circumstances? Are you making sure this won't be abused? 4. Determine whether you'll allow nitpicks. While I strongly suggest taking nitpicks out of the review (because most are subjective or can be fixed before the review), state if you'll be allowed to bring up nitpicks in a review at all. If you do, be sure to use the "nitpick: or nit:" prefix and explain what should be considered a nitpick.  5. What's allowed to block a review? Clarify what can block a #PR from being approved (and ultimately, merged into prod): Security issues? Missing tests? Missing documentation? Readability? Something else? The clearer your team is about blocking vs non-blocking issues, the fewer your debates will be during the #codereview. By drafting your own Team Working Agreement, you can start to make reviews less painful and more productive. And remember, you can always revisit this document and make changes as your team evolves. Just make sure you discuss and agree to the changes as a team! Get a TWA template in my book: https://lnkd.in/dKwGg667 And follow (theLGTMBook to be a better #codereviewer! https://lnkd.in/gJaDvkEu

Twelve years ago, I left a dream role building robotic dogs at Boston Dynamics to create a new class of robots that could solve construction’s biggest problems. I didn’t know what to expect as a founder in such a specialized space - how to raise funding, build a prototype, or assemble a team that could bring the vision to life. After eight years leading Canvas, my perspective and priorities have changed drastically. Here are the three biggest things I would tell any new founder in robotics: 1. Quantify Customer Needs Early Everything revolves around understanding and quantifying what your customer needs early and fast. Customers often can’t do this for you. Listen closely, study their workflow, define measurable outcomes, and share those metrics back, including price. Even if you’re off at first, it sparks the right conversation and ensures you know what to build. 2. Build for Reliability Hardware cycles are long, and you only get a few builds - pivoting isn't easy. That makes prioritization critical. Reliability is a critical and often overlooked customer need. It generally requires months of focus beyond the initial design and build to get right. Make it part of your plan from day one. 3. Set a few Clear Goals, then Hyperfocus on Them Your team is most motivated when they have clear, focused goals. Focus creates alignment and momentum. The team’s work is rewarded when customers love what they build — and that’s only possible if they understand what success looks like. Most importantly: hardware is hard. Robots are hard. That’s the reality and the opportunity. Embrace it, roll with it, and you might build something that changes everything.

Git Pull Request Workflow 0. 𝐒𝐭𝐚𝐫𝐭 𝐰𝐢𝐭𝐡 𝐚 𝐂𝐥𝐞𝐚𝐧 𝐒𝐥𝐚𝐭𝐞 ➟ Before beginning any work, ensure your local repository is synced with the latest code from the remote main branch. git checkout main git pull origin main ➟ Create a descriptive branch for your feature or fix git checkout -b feature/add-user-authentication ➟ Use a clear, consistent naming convention for branches (e.g., feature/, bugfix/). 1. 𝐌𝐚𝐤𝐞 𝐋𝐨𝐠𝐢𝐜𝐚𝐥, 𝐀𝐭𝐨𝐦𝐢𝐜 𝐂𝐨𝐦𝐦𝐢𝐭𝐬 ➟ Develop your feature or fix in small, logical chunks. ➟ Each commit should address a single, meaningful unit of work. git add src/auth/ git commit -m "Ticket 1234: implement JWT token generation" 2. 𝐏𝐮𝐬𝐡 𝐘𝐨𝐮𝐫 𝐁𝐫𝐚𝐧𝐜𝐡 𝐭𝐨 𝐑𝐞𝐦𝐨𝐭𝐞 ➟ Once you’ve completed your local changes, push your branch to the remote repository. git push -u origin feature/add-user-authentication ➟ Create a pull request (PR) through your Git platform (e.g., GitHub, GitLab, Bitbucket). Include: - A clear title summarizing the change. - A detailed description explaining the purpose, implementation, and potential impacts. - Links to related tickets, issues, or documentation. - Screenshots or videos for UI/UX changes. 3. 𝐂𝐨𝐝𝐞 𝐑𝐞𝐯𝐢𝐞𝐰 𝐏𝐫𝐨𝐜𝐞𝐬𝐬 ➟ Automated Checks - CI/CD pipeline should run tests, linting, and static analysis to validate the code. ➟ AI augmented Feedback - Tools like CodeRabbit can provide immediate, context-aware suggestions for: - Code style inconsistencies. - Common bugs or anti-patterns. - Security vulnerabilities. - Performance optimizations. ➟ Human Review - Teammates should evaluate: - Architecture and design. - Maintainability and scalability. - Alignment with business logic and requirements. - Adherence to coding standards. Tip: ➬ Encourage open, constructive discussions during reviews. ➬ PRs are an opportunity to collaborate and improve, not a battleground. 4. 𝐊𝐞𝐞𝐩 𝐘𝐨𝐮𝐫 𝐁𝐫𝐚𝐧𝐜𝐡 𝐔𝐩 𝐭𝐨 𝐃𝐚𝐭𝐞 ➟ Keep your feature branch synced with the target branch (e.g., main) to avoid conflicts later. 5. 𝐅𝐢𝐧𝐚𝐥 𝐏𝐫𝐞-𝐌𝐞𝐫𝐠𝐞 𝐂𝐡𝐞𝐜𝐤𝐥𝐢𝐬𝐭 ➟ Before merging your PR, ensure the following - ✅ All CI checks pass (tests, linting, builds). ✅ Required approvals are obtained from reviewers. ✅ All review comments are addressed with follow-up commits. ✅ Documentation is updated (e.g., README, API docs). ✅ The branch is up to date with the target branch (perform a final rebase if necessary). 6. 𝐌𝐞𝐫𝐠𝐞 𝐭𝐡𝐞 𝐏𝐑 ➟ Choose the appropriate merge strategy based on your team’s workflow - - Squash Merge [Combines all commits into one for a clean history.] - Rebase Merge [Maintains a linear history while preserving individual commits.] - Merge Commit [Creates a merge node, preserving the full commit history.] ------- Remember, A good PR isn’t about showing how much you’ve done, it’s about making it easier for someone else to understand and build on your work. 🤗 #git

Maintaining quality in Solar EPC (Engineering, Procurement, and Construction) projects is crucial for optimal performance, long-term reliability, and higher energy generation. Here’s how you can ensure top-notch quality at every stage: 1. Pre-Construction: Planning & Design ✅ Site Assessment & Feasibility Study – Conduct thorough shadow analysis, soil testing, and wind load assessment to determine optimal plant design. ✅ High-Quality Engineering Design – Use advanced simulation tools (PV*SOL, PVSyst) for accurate energy yield predictions. ✅ Compliance & Standards – Follow MNRE, IEC, IS, and BIS guidelines for quality and safety compliance. 2. Procurement: Sourcing High-Quality Components ✅ Tier-1 Solar Panels – Ensure high efficiency (>20%) and degradation warranties from reputed manufacturers. ✅ Certified Inverters – Choose high-efficiency inverters with robust MPPT (Maximum Power Point Tracking) capabilities. ✅ Quality Mounting Structures – Use corrosion-resistant, galvanized steel or aluminum to withstand harsh weather. ✅ Reliable Balance of System (BoS) – Use IS-certified cables, circuit breakers, and protection devices to minimize system failures. 3. Construction: Best Installation Practices ✅ Skilled Workforce – Train installation teams on proper wiring, earthing, and mechanical structuring to avoid long-term faults. ✅ Proper Cable Management – Use UV-protected cables, secure routing, and waterproof junction boxes to prevent faults. ✅ Standardized Installation – Follow IEC 62446 & IEEE standards to ensure safe and optimized installations. 4. Testing & Commissioning ✅ Pre-Commissioning Inspection – Conduct visual inspections, thermal imaging, IV curve tracing, and insulation resistance tests before energization. ✅ Performance Testing – Verify actual energy generation vs. estimated output through PR (Performance Ratio) analysis. ✅ Load Testing & Safety Checks – Ensure earthing, lightning protection, and grid synchronization before final handover. 5. Post-Commissioning: O&M & Monitoring ✅ Remote Monitoring – Implement SCADA or IoT-based real-time monitoring systems for efficiency tracking. ✅ Preventive Maintenance – Conduct regular cleaning, thermal inspections, and inverter servicing to minimize downtime. ✅ Warranty & AMC Compliance – Ensure adherence to OEM warranties and offer Annual Maintenance Contracts (AMC) for extended system life. By prioritizing quality control at every stage, EPC contractors can maximize ROI, improve plant efficiency, and ensure long-term sustainability.

if (!high_Quality_Code_Review) { code_Quality.suffers(); } The biggest challenge when it comes to code reviews is time. We all want to provide thoughtful feedback that improves the codebase without spending endless hours dissecting lines of code. – Deliver high-quality feedback. – Do it efficiently. – Minimize the back-and-forth between the author and reviewer. Here’s how to do it: 1. Start with the Change Description Always start with the PR (Pull Request) Description: ↳Understand the Goal: What problem is this change solving? Why is it necessary now? Does it align with the product or technical vision? ↳ Key Design Insights: Look for architectural decisions and trade-offs. Is the proposed solution justified, or are there better alternatives? ↳ Clarity Check: If the PR description needs to be more specific or complete, request the author to refine it. It’s better to clarify the intent than to misunderstand the implementation. 2. Focus on the Interface First Now, move on to the interface, not the implementation. ↳Abstraction: Does the interface present a clean abstraction? Is it intuitive for others to use? A good abstraction hides unnecessary details and provides a natural way for other parts of the system to interact with the component. ↳ Naming Conventions: Are the names of methods, classes, or variables clear and self-explanatory? Names should reflect their purpose without needing additional comments. ↳Contracts: -Does the interface define clear inputs, outputs, and side effects? - Inputs and Preconditions: What does the function or class expect? - Outputs and Postconditions: What does it guarantee? - Side Effects: Are there implicit changes, such as modifying global state? 3. Review the Implementation and Tests Last Once the interface is solid, dive into the implementation. Here’s how to structure your review: ↳ Correctness: –Does the implementation meet the intended functionality? –Test it against the stated goals in the PR description. ↳Edge Cases: Does the code handle unexpected inputs gracefully? –What happens if something goes wrong (e.g., network issues, null inputs)? – Can someone unfamiliar with the change understand the logic quickly? –Use proper indentation, modularization, and logical flow. –Is the solution simpler than necessary? ↳Efficiency: Does the code perform well under expected load? - Are there any unnecessary loops or expensive operations? - Is memory or CPU usage optimized? ↳ Test Coverage Checklist - Do the tests cover all important scenarios, including edge cases? - Tests should be simple and obvious. Avoid abstracting tests too much, even if it involves repetition. - If this change fixes a bug, ensure there’s a regression test to prevent it from resurfacing. - For changes with performance implications, validate them under real-world conditions.

9 code review practices your team should follow to go from Good → Great projects. (these helped my team deliver 100s of projects without wasting hours fixing bugs) 🟢As a team: ➡️Establish goals and expectations beforehand: for example: + functional correctness + algorithmic efficiency + improving code quality + ensuring code standards are met ➡️Use code review tools Use: (GitHub PRs, GitLab MRs, and Atlassian Crucible). + easily track changes + streamline the review process ➡️Automate code checks:  It will help you to: + find syntax errors + avoid common issues + reduce code style violations and potential bugs. 🟡As a reviewer: ➡️Start early, review often:  do this to: + catch issues early + prevent technical debt + ensure that code meets project requirements. ➡️Keep reviews small and focused:  you get: + an easier process + shorter turnaround time. + better collaboration in the team ➡️Balance speed and thoroughness:  + do comprehensive reviews  + but avoid excessive nitpicking ➡️Give constructive feedback: always be: + specific, actionable, and respectful + focus on improvement rather than criticizing.  + make a space for open communication to answer questions & give clarifications. 🟠As a reviewee: ➡️follow up on feedback:  + don’t take the comments personally + actively work on feedback after the session + make necessary revisions and follow up to confirm ➡️Follow coding standards:  focus on improving: + readability + maintainability Remember - mutual respect during the code reviews is crucial for a great team culture! – P.S: If you’re a Sr. Software engineer looking to become a Tech Lead or manager. I’m doing a webinar soon. Stay tuned :)

🔧 Step-by-Step Guide to Solar PV System Installation ☀️ Installing a Solar PV system is more than just placing panels on a roof — it's a detailed process that demands precision, safety, and expertise. Here's a breakdown of the key stages to ensure optimal system performance: 1️⃣ Site Assessment & Load Analysis Evaluate solar potential, energy consumption patterns, and structural integrity. 2️⃣ System Design & Sizing Determine capacity, choose components, and size based on load and sunlight availability. 3️⃣ Component Selection Choose high-quality PV modules, inverters, mounting structures, cables, and batteries (if off-grid or hybrid). 4️⃣ Permitting & Approvals Secure local authority approvals and utility interconnection agreements (for grid-tied systems). 5️⃣ Mounting Structure Installation Fix racking/mounts securely with proper tilt and orientation for maximum efficiency. 6️⃣ PV Module Installation Install panels safely and uniformly, ensuring proper cable management. 7️⃣ Electrical Wiring Connect modules, inverters, protection devices, grounding, and control panels as per electrical codes. 8️⃣ Inverter & System Integration Connect the inverter, monitor, and battery (if applicable). Integrate with the load or grid. 9️⃣ Testing & Commissioning Conduct electrical tests, check performance, and verify system safety and efficiency. 🔟 Handover & Documentation Provide manuals, warranty documents, test reports, and train the end-user. 💡 Whether it's rooftop, ground mount, or hybrid — each project requires careful planning and skilled execution. As renewable energy professionals, let’s uphold quality, safety, and sustainability in every installation. Emmanuel Marindi #SolarInstallation #RenewableEnergy #SolarEnergy #PVSystem #SolarPower #GreenEnergy #EnergyEfficiency #Sustainability #SolarProjects #SolarDesign #CleanEnergy #GridTiedSystem #OffGridSolar #HybridSolar #SolarEngineering #ClimateAction #SolarPV #SolarExperts #SolarAfrica #SolarProfessionals