The lost timeline is where everything went perfect, where it all worked out, where nothing went wrong and things came together without a moment’s hestitation. Nothing went wrong. You were perfect. Your team was perfect. It’s a lost timeline, because it never goes this way so stop trying to force it to get there.
You want to reduce your lost sprints when it comes to building a release. Lost sprints happen – customer bugs come in and they derail everything you’re doing. Or a seemingly well-estimated bug blows up in your face and ends up becoming a feature that still needs to be done this sprint, but everything else will be pushed out. The sprint becomes lost when more and more of your team starts to work on these…
Problems are the bread and butter of your success. How many can you solve? How fast can you solve them? How do they scale? How much effort do they take? What is needed to fix them? When hiring, you always want problem solvers because no matter what they know, have on them or know through their network – they’ll be the ones to figure it out and that’s what you need.
I saw this picture the other day and it speaks volumes, not only for sports but for work as well. Your basics are what set you apart from everyone else. Knowing what they are is what makes you indispensable because then you can start focusing in on them, refining them, and making them stronger. But if you don’t know what your basics are, what your fundamentals are – then you’re just practicing everything, everywhere and…
Any piece of software has a set of configurations, toggles, and switches that make it come alive. The configuration is what makes the software work for your customer and makes it “their own, unique copy”. Four things a configuration should always have; A place to go and make the change, not forcing the customer to jump here, there, and everywhere. Settings that do what they are supposed to do. Be simple in their implementation, if…