At some point in a project, features will be cut (unless you have inifinite time, resourcs and absurdly patient customers). On a first release, it is inevitable – you’ve hit issues you didn’t expect, run up against the wall against problems you didn’t even know existed, when the user saw what they were getting they wanted to change things up, etc, etc. The list goes on. When this happens, the question that everyone has to…
This is one of those knives through the heart type of thing. You have a team working towards a delivery, everyone has their piece that they are responsible for. At the meeting to discuss where things are on the deliverable, the team clearly has a lot left to do and is working through how they are going to accomplish that. You’ve just gone through all the issues when someone chimes in – “My part is…
Wow, what a way to start a meeting. Why are we here? I had someone ask this at a meeting today and instantly felt like leaving. If you are leading a meeting, if you are in charge of a meeting and you don’t know why you have assembled people here. Than cancel the meeting. Not because they aren’t ready, but because you aren’t.
If everyone is using different apps to accomplish the same goal. Then no goal is being accomplished. No tool or app will ever be perfect, but they will be good enough. And good enough is what you need to ship. If you still don’t think it’s good enough and you continue to use multiple apps different then what everyone is using there is only one goal you are accomplishing. Holding your team back from what…
This is the hardest question when trying to figure out the “what” of what goes into a release, feature, story. “What is it that we are trying to do?” “What is it that our customer needs us to do?” It’s not an easy question for the singular reason that the answer won’t always jive with what we have in our head, what we had already planned, what we were already focused on. But if you…