Mike Lyons’ Post

You can lock scope, schedule, budget... and quality... but that doesn't mean you will succeed. Wanting something to be so doesn't make it so, regardless of how positively you think. Reality will bite. This all comes from a desire for control. Managers (and management) continue to believe despite all evidence to the contrary that arbitrarily locking all project parameters to (hopefully) eliminate variance is the key to control. Managers (and management) needs to realize that in non-repetitive knowledge work there is variance and ignoring this with wishful thinking dooms the org to failure. Therefore, focusing on reducing variance across the domains of work is essential to increasing predictability and control. Yet, too often managers insist on doing more of what doesn't work. I can give you predictability, with decreasing variance, across the life of a project... and in doing so give you (management) options. In the uncertain world we live in, that's as good as it gets. It's good enough, because nothing else is better. This capability will enable you to beat your competition with better products, lower development and support costs, happier development staff, and faster time to market. If this is what you want, DM me and let's start a conversation. #projects #projectmanagement #agile #scrum #kanban #productmanagement #productdelivery #management #leadership #execution

Question on reddit: "Isn't agile a mini waterfall ? Instead of planning and executing a complete requirements, we create a requirements enough to be finished within sprint duration? Which means any change to requirements or scope mid sprint should be treated similarly to any change or scope in waterfall?" Answer: "No, because scope MUST be flexible even during the Sprint. Let's use our trusty old friend the Project Management iron triangle to make this point. During the Sprint: - Resources are fixed (team size doesn't change and if it would increase or decrease, in both cases it would slow the team down during the Sprint, because people need time to get up and running). - Time is fixed (Sprint duration) - Quality is fixed (Definition of Done) So, given these constraints. The scope must be flexible. The goal of the Sprint, that's the intent: what are we trying to achieve and why does it matter? that acts as an anchor. Complex work means surprises means inevitable scope changes even DURING the Sprint. So, if anybody talks about surprises as 'scope creep', then they didn't get the memo.

Thank you, Maarten, for an engaging post and thoughtful discussion. Your post on whether Agile is just a “mini Waterfall” inspired me to reflect on Bob Wysocki perspective, as presented in his book Effective Project Management (https://lnkd.in/guVJxdYR). Wysocki provides a profound analysis of how project management methodologies differ, particularly in terms of flexibility and their ability to adapt to uncertainty. While Agile emphasizes flexibility within iterations (sprints), the distinction becomes clearer when compared to more linear approaches like Waterfall, where scope adjustments are far more rigid. Here’s a quote from Wysocki’s book that elaborates on the differences between Project Management Life Cycle (PMLC) models: Their differences are evident when viewed from the degree of solution uncertainty, as follows: • The models form a natural ordering (Linear, Incremental, Iterative, Adaptive, Extreme) by degree of solution uncertainty. • The processes that form repetitive groups recognize the effect of increasing uncertainty as you traverse the natural ordering. Those groups move more toward the beginning of the life cycle as uncertainty increases. • Complete project planning is replaced by just-in-time project planning as the degree of uncertainty increases. • Risk management becomes more significant as the degree of solution uncertainty increases. • The need for meaningful client involvement increases as the degree of solution uncertainty increases. I believe his analysis could further enrich this discussion and shed light on how we approach uncertainty in modern project management. I believe his insights could provide valuable context to this discussion.

When deciding between Agile and Waterfall, it's important you consider the specific needs and characteristics of your project. This report breaks down the key differences and offers advice on how to choose between the two. Take a look below. #Agile #Waterfall #ProjectManagement #ProfessionalServices #PSA https://lnkd.in/e6Rc8AvY

Hey network, I recently came across an insightful comparison between Agile and Waterfall methodologies, and I wanted to share some key takeaways. 📊 Agile Method: - Emphasizes continuous cycles of planning, designing, developing, and testing. - Features small, high-functioning, collaborative teams. - Promotes flexibility and continuous evolution. - Strong focus on customer involvement throughout the process. Waterfall Method: - Follows a sequential and linear progression through stages: Conception, Initiation, Analysis, Design, Development, Testing, and Deployment. - Requires thorough upfront planning and extensive documentation. - Best suited for projects with stable, unchanging requirements. - Relies on close involvement from the project manager. Each approach has its strengths and fits different types of projects. Whether you prefer the iterative agility or the structured linearity of Waterfall, understanding both methodologies enhances our ability to manage projects effectively and deliver value. Which method do you find more suitable for your projects? #Agile #Waterfall #ProjectManagement #ContinuousImprovement #Collaboration #SoftwareDevelopment #CustomerFocus #Scrum #Kanban #Lean #DevOps #SoftwareEngineering #TechLeadership #AgileTransformation #WaterfallModel #BusinessStrategy #Innovation #TeamWork #ProductDevelopment #ITManagement #ProcessImprovement #DigitalTransformation #AgileCoach #ProjectPlanning #ProjectExecution #SoftwareLifecycle #Methodologies

Can We Combine Waterfall and Agile Methodologies? 🤔 Yes, We Can! We can effectively create a hybrid approach that incorporates both waterfall and agile methodologies. Here’s how to start with the waterfall model in projects that require structured planning: 1- Define the Scope: Begin by outlining the general scope of the project. Understand the requirements thoroughly. 2- Create a Complete Vision: Develop a comprehensive vision for the project,considering all related dependencies. 3- Identify Stakeholders: Determine who the key stakeholders are. Discuss the vision with them to refine and enhance it further. 4- Set Implementation Priorities: Establish clear priorities for implementation, ensuring that the most critical tasks are addressed first. 5- Develop a Detailed Plan: Create a timeline that outlines the phases of implementation. During the implementation phase, apply the agile methodology throughout all stages of development. This will ensure we remain flexible and responsive, ultimately delivering a product that meets the end user’s needs #agile , #Project_management

Here are some differences between #Agile and #Waterfall methodologies in their approach to #project #management Agile: Iterative and Incremental: Agile breaks down projects into small, manageable chunks called iterations. Flexibility: Agile allows for changes in project scope throughout the development process. Customer Collaboration: Regular feedback from customers is encouraged and incorporated into each iteration. Continuous Delivery: Working versions of the product are delivered frequently, allowing for regular assessment and adjustments. Waterfall: Sequential Phases: Waterfall follows a linear and orderly sequence of phases such as requirements, design, implementation, verification, and maintenance. Predictability: It works well for projects with well-defined requirements and where changes are not expected. Documentation: Emphasizes thorough documentation at each phase before moving on to the next. Single Delivery: The final product is delivered at the end of the project timeline, after passing through all the sequential phases. In summary, Agile is suited for projects requiring flexibility and customer involvement, while Waterfall is better for projects with clear, unchanging requirements

#Agile is often the most suitable solution for #ProjectManagement. Nowadays, many projects have a vague scope upfront and must transform themselves to meet ever-changing demands. Agile allows development #teams to be flexible and respond promptly to changes by delivering what people want. That said, many cases still exist where #Waterfall can be attractive and enticing. In the post, I will draw a parallel with this consideration. #ProjectManagement #SoftwareDevelopment

🚧 AGILE VS. WATERFALL: WHICH METHODOLOGY REIGNS SUPREME IN APPLICATION DEVELOPMENT? 🛠️ "IS YOUR TEAM STILL TETHERED TO OUTDATED PRACTICES, OR ARE YOU RIDING THE WAVE OF AGILE INNOVATION?" 🤔💡 The debate between AGILE and WATERFALL continues to spark discussions. Each has strengths and weaknesses, influencing project success. AGILE: FLEXIBILITY: Quickly adapts to changes. 🔄 FASTER DELIVERY: Smaller iterations mean quicker releases. ⏩ COLLABORATION: Enhances communication within teams. 👥✨ WATERFALL: STRUCTURED: Clear stages for large projects. 📊 DOCUMENTATION: Reduces ambiguity. 📝 PREDICTABILITY: Better for fixed requirements. 📅 As developers, we must choose the right methodology based on project needs. WHAT’S YOUR EXPERIENCE WITH AGILE AND WATERFALL? LET’S DISCUSS! 💬🔍 #Agile #Waterfall #ApplicationDevelopment #ProjectManagement

Agile vs. Waterfall: Which Development Methodology Fits Your Project? When it comes to software development, choosing the right methodology is key to project success. Here’s a quick comparison: Waterfall: A linear, step-by-step approach. Once a phase is completed, there's no going back. It's great for projects with clear, unchanging requirements. Agile: An iterative, flexible approach. Work happens in sprints, allowing teams to adapt as requirements evolve. Perfect for projects that need quick adjustments and continuous improvement. 💡 Waterfall is best for stable, predictable projects. 💡 Agile is ideal for dynamic, evolving projects. Which methodology do you prefer for your business? Let’s discuss! And if you need help choosing the right approach, feel free to DM me! #Agile #Waterfall #ProjectManagement #SoftwareDevelopment #BusinessStrategy