Fred Schenkelberg’s Post

Is Detailed Design Anti-Agile? https://lnkd.in/dbpShVPz A CERM Risk Insights article by Howard Wiener, MSIA, CERM. Discover the benefits of agile and detailed design for systems development projects. Learn how it can save time, reduce errors, and increase flexibility.

System agnostic requirements and "outcome based interaction" talk by Arjan Noordhoek at the the #EventModeling #unconference. Excellent explanation about why design allows solutions to be proposed with the most knowledge available as opposed to #agile and #waterfall.

When Agile and Earned Value Management Collide: 7 Considerations for Successful Interaction https://lnkd.in/eMguddvA Pat Place and Stephen Wilson discuss seven considerations for successful use of #agile and #evm.

Don‘t do this! The real SAD CI/CD process. Please: 👉 Keep branching to a minimum and branches short-lived – ideally don‘t branch at all. 👉 Apply a test-first approach (TDD) and invest heavily in automated tests. Trust me, it‘ll make you faster faster than you can say faster. 👉 Just apply some common sense and let developers do their job professionally. Don‘t force a process onto them so management gets better control. These devs are professionals ffs. #tdd #agility #cicd

If an item is blocked for weeks, do you keep it in the same column and allow it to occupy the WIP in that column, or is it more convenient to move it to a dedicated blocked column? Your workflow should represent your knowledge discovery process. It should contain the activities that your team is performing to deliver customer value. Having a blocked column contradicts the nature of a workflow. It communicates that blocking work is a standard step in your delivery process. By discarding the blocked column and keeping the blocked cards in the column the blocker occurred, you are occupying WIP and, therefore, keeping the attention on the impediment that slows you down. It is better to allow the WIP to continue to be consumed so the team can focus on unblocking the issue. Furthermore, strive to treat your defects in the same way you treat your blockers. Defects can be managed like blockers to investigate their root causes and solve them in an economically sensible way. To learn more about the 4-step process to effective defect management, download our guide to sustainable delivery of quality software → https://bit.ly/3sviOcD #NavigateYourFlow #Kanban #Quality #Agile #ContinuousImprovement #DefectManagement #SoftwareDevelopment

If an item is blocked for weeks, do you keep it in the same column and allow it to occupy the WIP in that column, or is it more convenient to move it to a dedicated blocked column? Your workflow should represent your knowledge discovery process. It should contain the activities that your team is performing to deliver customer value. Having a blocked column contradicts the nature of a workflow. It communicates that blocking work is a standard step in your delivery process. By discarding the blocked column and keeping the blocked cards in the column the blocker occurred, you are occupying WIP and, therefore, keeping the attention on the impediment that slows you down. It is better to allow the WIP to continue to be consumed so the team can focus on unblocking the issue. Furthermore, strive to treat your defects in the same way you treat your blockers. Defects can be managed like blockers to investigate their root causes and solve them in an economically sensible way. To learn more about the 4-step process to effective defect management, download our guide to sustainable delivery of quality software → https://bit.ly/3sviOcD #NavigateYourFlow #Kanban #Quality #Agile #ContinuousImprovement #DefectManagement #SoftwareDevelopment

🚀 𝐄𝐥𝐞𝐯𝐚𝐭𝐢𝐧𝐠 𝐒𝐨𝐟𝐭𝐰𝐚𝐫𝐞 𝐃𝐞𝐯𝐞𝐥𝐨𝐩𝐦𝐞𝐧𝐭 𝐰𝐢𝐭𝐡 𝐂𝐡𝐚𝐧𝐠𝐞 𝐂𝐨𝐧𝐭𝐫𝐨𝐥 𝐁𝐨𝐚𝐫𝐝𝐬 (𝐂𝐂𝐁) 🚀 Just like the Architecture Review Board (ARB), the Change Control Board (CCB) is crucial in software development, ensuring streamlined and governed changes within the project roadmap. 𝐖𝐡𝐨'𝐬 𝐈𝐧𝐯𝐨𝐥𝐯𝐞𝐝? - Developers, Product Managers, Designers - Solution & Product Architects - Testing & QA Teams 𝐖𝐡𝐲 𝐈𝐭'𝐬 𝐕𝐢𝐭𝐚𝐥: - Ensures alignment with project goals and requirements - Prevents adverse impact on the current product - Maintains roadmap integrity - Aligns development with product goals 𝐊𝐞𝐲 𝐁𝐞𝐧𝐞𝐟𝐢𝐭𝐬: - Strengthened project oversight - Enhanced risk management - Strategic alignment with goals - Ensured customer satisfaction for intermediate or special deliveries The CCB is key to project success, emphasising its importance in all software development efforts. #ChangeControlBoard #SoftwareDevelopment #ProjectManagement #TechLeadership

Should You Document Requirements? Agile vs. Detailed Specs. Check us out-https://bit.ly/3T5OljC Ever debated the need for requirements documentation? This video explores factors to consider when deciding between high-level & detailed approaches. Watch the video here- https://bit.ly/3U5wjQA #requirements #businessanalysis #projectmanagement #agile #softwaredevelopment #techcanvass

Good, fast, cheap. Only the best in the business get to pick two. Often even they have to settle for just one, given the circumstances. But very frequently, you quite simply get none of them. The world is full of projects that drag on, cost a fortune, and don't deliver what was promised. One of the best things about agile/lean/whatever that is lost in SAFe is that you get "quick" almost for free because you are supposed to be delivering value quickly - even if it's not much. That means, regardless of where you are with the other two, that you can reassess and pull out of a boondoggle. Yes, it means throw-away code, or rework, or letting stakeholders down (Pivot Triggers are a good way of avoiding this last one). But it's better than the alternative. 

Should You Document Requirements? Agile vs. Detailed Specs. Check us out- https://bit.ly/3T5OljC Ever debated the need for requirements documentation?  This video explores factors to consider when deciding between high-level & detailed approaches. Watch the video here- https://bit.ly/4aw4Ts9 #requirements #businessanalysis #projectmanagement #agile #softwaredevelopment #techcanvass