In starting work on a new feature, story, use case, issue, etc, etc – there is generally some point where you are going to get confused. Perhaps it’s a new requirement, perhaps its a new concept you’ve never heard of or maybe, despite all the time that’s been invested, it’s written in such a way as to not evoke clarity in what you need to work on, there is one simple question which will give…
Whenever we write requirements, we start off with a great big vision that we want to achieve. This is great in theory but when people read it, especially if they are mid to end of the release and work is not going well, they instinctively push it aside for – “nice to haves”, “if we can get to it”, “maybe next sprint”. But if we switch our mindset and instead write our features as challenges…
On this week’s episode of Remotely Prepared – we talk about all the announcements that have been coming out as of late on the big companies going remote. Oddly enough, it sounds like we are ripping it to shreds whereas we do think it’s great. The way I am thinking about this big, monumental change in my mind is that if everyone decided they were going to switch from iPhones to Android – would we…
Don’t be fooled into thinking there is only one speed and that is the only speed of innovation, creativity, ambition, excellence, perseverance, direction and vision which culminates into momentum. There are many speeds to momentum, we all have it, we all go different speeds depending on the issue being worked on and resolved to. It’s not a race, if it was we all we would have loss, because when we boil it down to what…
When a light goes down at an intersection, one of two things will occur. Either the system’s back-up response will kick in that everyone knows and understands or a new response will take shape. In the case of a light going down the back-up response here is everyone waiting their turn, while they wait for the next person to go (on their right). The process isn’t perfect, traffic is slowed down, but it goes, it…