Plaky’s Post

Thoughts: Why Project Estimates Fail Let's talk about project and feature estimation once again. Last time, we discussed how teams often miss estimates in the early stages. This time, let's observe the risks that materialize when working within integrators. From my experience, estimates are not met when: - The estimate was made by a different team that is partially or fully uninvolved in the project. - The features are large and contain or exclude things that may seem obvious only to you. For example, in an IT project, a feature might assume the existence of certain infrastructure which isn't actually in place. - The technology/library was changed to "almost the same, but better/newer." This results in time spent learning and dealing with unforeseen issues. - The involvement of BA/Dev/QA is automatically calculated without considering specific needs. Eliminating these fundamental causes can significantly enhance accuracy: 1️⃣ Review and challenge external estimates. If it’s not possible to challenge them directly, document your concerns and identified risks via mail/chat. 2️⃣ Break down large features into smaller ones: this makes it easier to define assumptions and limitations, and later, to decompose them. 3️⃣ Don't be optimistic. Avoid changing the approach and technology mid-project without reassessing the estimates. 4️⃣ Adjust automatic calculations if there are many risks and the feature is cross-functional. For instance, QA might need more time if the feature changes data source algorithms for interconnected systems. ❓ Shall we continue the discussion on why estimates often miss the mark?

Excellent material that is worth your time. A systematic approach that generates a structure for the developer to design, create and deliver high-quality software based on customer requirements and needs. The primary goal of the SDLC process is to produce cost-efficient and high-quality products. The process comprises a detailed plan that describes how to develop, maintain, and replace the software.

Concise representation of the SDLC phases

Why We Miss the Mark on Estimates Estimates, darn it, they’re imprecise. You always seem to fall short. Even when you double up as a buffer, it's still easy to miss the target. And while no one outright approves a doubling, each subsequent manager tends to tack on an additional 30% just to be safe. As a result, by the end, it turns out to be both double and triple whatever you originally planned. - How can we hit our estimates more accurately? - A deeper understanding of the subject and the conditions of the estimate is crucial. The more we know about a project, the more accurate our estimates become. Remember how wide the variance can be at the start of each project? In the first 3-4 sprints, deviations of even 30-40% can occur. (Experienced managers at this point promise dramatically less, but that’s a story for another day). Then, a year or half a year later on the same project with the same team, the variance is at most 5-10%. Why is that? It's because over time we learn a lot more about what we're dealing with and mitigate risks: 🤞 Will this library work as expected? 🤞 Is that front-end developer as skilled as his resume suggests? 🤞 How often will the software change tasks during a sprint, and how well are they fleshed out? So, project knowledge naturally accumulates over time, and with it, the precision of estimates improves. In principle, you could just go with the flow, and over time, estimates will become slightly more accurate. But that’s something every junior knows how to do, so next time we’ll discuss some tricks a PM can use to speed up this process.

📣Transform Your Next Sprint with the RIBS Approach! Are you looking to streamline your software development process and ensure every component is perfectly aligned with your business objectives? If you’re new to the concepts of UML (Unified Modeling Language) and the RIBS approach, our next sprint could be the game-changer you’ve been waiting for. 🤔What is RIBS? It stands for Requirements, Interfaces, Business Rules, and Structure. This methodology helps you define and refine your software projects, ensuring clarity and efficiency from conception to deployment. Here’s a quick breakdown: - Requirements: Define what your software must do and the boundaries within which it must operate. - Interfaces: Specify how your components will interact, both within the system and externally. - Business Rules: Determine the operations and logic that dictate how your application behaves. - Structure: Outline the architecture of your project to support its functionality and future scalability. Why Try RIBS? - Clarity and Precision: By breaking down your project into these four components, you ensure that every piece is clearly defined and serves a specific purpose. - Efficiency: This approach can save you time and resources by preventing unnecessary rework and focusing on essential features. - Adaptability: RIBS is flexible and can be integrated at any stage of development, making it perfect for sprints. 🤷Not Familiar with UML or RIBS? No Problem!🤷 If you're intrigued but unsure how to start, I’m here to help. I invite you to test the RIBS approach in your next sprint. It’s a powerful way to enhance your project management and development strategies. If you need guidance or wish to discuss how to implement this method in your projects, don't hesitate to reach out. Let’s make your next sprint the most structured and efficient yet! 💡Ready to revolutionize your development process? Let's dive into RIBS together!💡

“Individuals and interactions over processes and tools”. Effective stakeholder engagement skill to gather requirements, prioritize them based on value, navigate conflicts, risks and align stakeholders’ expectations to meet the overall vision and goals, should be one of the most important (if not the most important skill), a Scrum Master, Product Owner and Business Analyst should have. This can be achieved by facilitating open communication and collaboration with the stakeholders that impact and are impacted by the project using various elicitation techniques to ensure that the “processes and tools” used deliver the expected results at the end of the lifecycle. #sdlc #predictive #adaptive #hybrid #scrummaster #businessanalyst #productowner #waterfall #agileframeworks

📊💡 SDLC Phases Infographic: A Roadmap for Success. Phase 1: Formation 🏁 - Project Initiation 🚀: Define project scope, objectives, and feasibility. - Rough Order of Magnitude (ROM) Estimate 💰: Create initial project estimate. Phase 2: Requirement/Planning 📝 - Requirements Definition 📋: Gather and document project requirements. - Project Management Plan (Charter) 📑: Establish project plan and charter. - Functional Requirements 🛠️: Define system's functional specifications. - Technical Requirements 💻: Identify technical specifications and constraints. - Requirements Review & Approval ✅: Review and approve project requirements. Phase 3: Design 🎨 - Internal/External Design 🌐: Create system's architectural design. - Design Review 👀: Conduct thorough design review. - Detailed Project Development 📅: Develop detailed project plan. Phase 4: Construct 🛠️ - Prototype 🏗️: Build working system prototype. - Code Review 🧾: Review and refine codebase. Phase 5: Test 🧪 - System Test 📊: Conduct comprehensive system testing. - Test Summary 📊: Summarize test results and address issues. Phase 6: Product Release 🎉 - Operational Acceptance ✅: Obtain stakeholder approval for final product. - Acceptance Document 📄: Document acceptance criteria and sign-off. Phase 7: Post Implementation 🌿 - Enhancement Maintenance 🛠️: Provide ongoing support and enhancements. - Project Implementation Notice 📧: Communicate project completion and implementation details. Throughout the SDLC, documentation 📚 and training 🎓 are crucial for a smooth transition and knowledge transfer. The Change Control Process ♻️ emphasizes managing scope changes effectively. Proposed changes go through rigorous evaluation and approval to maintain project stability. By following this well-defined SDLC framework, streamline your software development efforts, improve collaboration, and deliver exceptional results.

Writing requirements well can be the make-it-or-break-it factor between a successful project and a failed endeavor. Why? Poorly written requirements can lead to costly mistakes and delays. Often, the reason behind that is scope creep, which is when a project’s scope changes or grows in an uncontrolled way after the project has already started. Sadly, this is pretty common if the project scope is not well defined, documented, and controlled by high-quality requirements authoring from the start. #PTC #ALM #Codebeamer #RequirementsManagement Tushar Ghosh Mohammed Asif Ansari

Unravelling the Maven POM: Your Guide to Effective Project Management! Explore my latest Medium blog for essential insights and best practices. #Maven #POM #ProjectManagement https://lnkd.in/gXaCKWZ9

Understanding BRD vs FRD: Key Differences and Importance Are you familiar with the crucial documents shaping the success of software development projects? Let's delve into the differences between BRD (Business Requirements Document) and FRD (Functional Requirements Document) to enhance your project management knowledge! BRD (Business Requirements Document) outlines high-level business objectives, goals, and needs. It focuses on the "what" rather than the "how" of a project. BRD serves as a communication tool between stakeholders and development teams, ensuring everyone is aligned on project scope and objectives. FRD (Functional Requirements Document), on the other hand, delves into the specifics of how the system will function to meet the business requirements outlined in the BRD. It defines detailed functionalities, features, and technical specifications necessary for system development. Understanding the disparities between BRD and FRD is pivotal for project success. While BRD sets the overarching business goals and expectations, FRD translates these into actionable technical requirements for developers. Why is this important? Clarity and Alignment: BRD ensures stakeholders are on the same page regarding project goals, while FRD provides developers with clear instructions for implementation. Risk Mitigation: Detailed requirements in FRD help identify potential issues early in the development process, reducing the risk of costly rework later on. Efficient Development: By clearly defining requirements, both documents streamline the development process, saving time and resources. Key Takeaways: BRD defines business objectives. FRD translates business requirements into technical specifications. Both documents are essential for successful project execution. Remember, a comprehensive understanding of BRD and FRD can significantly enhance your project management skills and contribute to the success of your projects! 💼💻 #BusinessAnalysis #ProjectManagement #BRD #FRD #SoftwareDevelopment #RequirementsEngineering #StakeholderManagement #TechDocumentation #LinkedInLearning #ProjectSuccess