Start simple with Git.
With feature branches on the main branch: GitHub Flow.
But consider this 🤔:
Why create a branch for a feature that can be built in one day?
Is it a convention we mindlessly follow or a useful practice?
Consider working directly on the main branch 🎯 for smaller tasks. The simplicity might surprise you. 😯
Get out of the comfort zone ⚠️ and question the processes. What’s your take on it? 💭
Power Platform Advisor
Microsoft Power Platform Advisor with over 25 years of experience in IT with a focus on (marketing) automation and integration.
Helping organizations with scaling their business by automating processes on the Power Platform (Dynamics 365).
Expert in Power Platform, Dynamics 365 (Marketing & Sales) and Azure Integration Services. Giving advice and strategy consultancy.
Services:
– Strategy and tactics advise
– Automating and integrating
A daily newsletter on automation and eliminating friction
Backlog: The Black Hole of ideas Is your backlog turning into an ever-expanding universe of forgotten dreams? We all know that mix—a jumble of big ideas and tiny tasks waiting for their day in the sun. Some items linger for years. Why do backlogs grow? Because we...
The Trade-off Between Budgets and Quality ⚖️ In my previous post, I talked about shifting from Estimates to Budgets for feature development 💡. Let's dive deeper. Using a Budget instead of an Estimate introduces a trade-off: Scope and Quality adjust to fit the time...
Budgets instead of Estimates Estimating a feature is difficult and is often a guess (or even a lie). An Estimate is for a fixed scope. So, you need to think deeply how to implement the feature, before giving an Estimate. The business can then use the Estimate to...