The idea of sprints, retrospectives, and alike is all a waste of time. In the early days, we had waterfalls, and it was horrendous for reasons that contrast with the in vogue agile-ish ceremonies...
Peeps, let's be clear: the Agile manifesto intention, in my understanding, is so we don't forget to (re)validate ideas, gather feedback from last shipped work, and ensure all stakeholders are still aligned on expectations. The idea is to continuously ship increments and/or modifications to the project and adjust back if necessary (from feedback). The smaller the unit of deployment, the quicker we can course correct!
Sprints, as a way to measure how long something's going to take to be ready, is a fallacy! It's just estimates badly disguised as something else... There's absolutely nothing in this world we can measure or calculate that would give us a real timeline of the duration of something that takes longer than a week - and this is already pretty unpredictable.
"Oh, José, but we do need to know how long something might take, so we can plan our 12-18 months roadmap for the company". No... What you need is:
1. A mission: what will the company aim for in a given period?
2. A set of initiatives: how do you, collectively as a team, intend to help achieve that mission? Distribute that evenly per quarter.
3. Projects per initiative: how can the initiative be decomposed into small deliverables? Distribute that evenly per month.
4. Tasks: what you need to do, individually, to complete a project. Distribute that evenly per week.
Review, re-evaluate, and course correct constantly to understand how the company is going:
- Each week: what tasks have been done/not done?
- Each month: how are projects doing? Is there any expected delay due to tasks that haven't been done yet? Is there anything to be done to improve that? Hiring, re-scope work, drop things?
- Each quarter: how are the initiatives? Are they having a positive impact on the mission? No? Do you need to course correct it?
- Each year: how's the mission? Is it achieved? Did any priority change due to market behavior?
Laravel Herd for Windows is now available 🚀
We've been working on this for the last couple of months and I couldn't be more excited!
✨ One-click PHP updates
🔒 Secure/Unsecure your local sites
🏝️ Isolate sites
💻 NVM integration
and SO much more!
https://t.co/7htWix5nQ1
October CMS 3.5 is here! 🎉 Now with Multisite Groups for all your language needs, smart Multisite Mailer, sleek Nav Improvements, Stackable Popups for smooth UX, a quick Color Mode Switch, SEO-friendly Resizer Filenames, and more. Upgrade now! Details: https://t.co/c3lU1MSYrt
🎉 After weeks of development, @gehrisandro and I are proud to announce the release of OpenAI PHP Client v0.1. 🚀
It's a supercharged PHP API client that allows you to interact with @OpenAI API. Enjoy! ⚡️ https://t.co/7Gw0fewlSx
Today, I'm so happy to officially announce a new category of courses at Laracasts, called CreatorSeries. (And the first one is ready to watch in its entirety...)
Learn all the details here:
https://t.co/mzZdxJ3G4H
October CMS version 3.0.45 has just been published! Among other important updates, it includes a brand new AJAX framework that eliminates the jQuery dependency in October CMS themes and makes the website pages faster thanks to Turbo Router technology. https://t.co/H7fML2iDoW
I was in the process of writing a book on API development in Laravel, but after giving it some thought I have decided that I am going to give this for free.
With developers spending so much to stay current on courses, subscriptions etc - I want to finish this for free.
Webinar "CAREER PATHWAYS AND GREEN ECONOMY"
May 17th, 10h00 - 11h00 (Lisbon time) / 11h00 – 12h00 (CET).
Free, Online and in English.
https://t.co/rUk0FzwdQw
I'm working on a Laracasts series called "Livewire Uncovered" where I build a working version of Livewire from scratch.
Kinda nuts how little JavaScript I ended up with in the end to make the whole thing work 🤯
If you're having trouble upgrading an old, say, Laravel 5 project to the latest release, you may find that it's much easier to instead create a brand new Laravel project and then copy over your application files.
Depends on the project, but could make for fewer headaches.