Questions you'd be crazy not to ask at the start of your next project
11–14 of 14 posts
[deleted]
Re: Questions you'd be crazy not to ask at the start of your next project
#12Earlier quoted context omitted.
You forgot the tags. At least I hope this was intended sarcastically.
No, I am serious. The graphics were not your standard clip/stock art I thought they added to the message. If you don't, that's fine but there's no reason to be rude or disrespectful about it.
The team must be so agile they didn't proof-read it.
Re: Questions you'd be crazy not to ask at the start of your next project
#13I hate to rag on TW, and I know they're good folks, but I've had about six teams that went through their Agile Inception process, and I was less than impressed by the results. Don't get me wrong -- I think these are great questions. I think you need to ask them. And the TW guys meant well. In fact, the teams really enjoyed the exercise. It just wasn't as helpful as it could be. I think that this is not related to the…
I agree with your checklist point. I've witnessed smart, creative people abandon thought and agility to complete a checklist. I've personally struggled with this issue in our business development process. When we're meeting with a new client, I get so excited about their project, that I dive into technical details and forget to ask fundamental questions about milestones, schedule, resources, etc. But when I have a checklist in front of me to ensure I ask these questions, I'm too focused on the list and miss important details specific to the project. We've found that a decent compromise is to have at least two people from our side at every meeting. One is dedicated to scenario-specific quick thinking and the other more mechanically ensures we've covered the fundamentals. It's still not perfect for some of the other reasons you mention, but having only one person in charge of the checklist and having others be checklist-free seems to allow for a good mix of agility while ensuring the critical parts of our process are followed.
Re: Questions you'd be crazy not to ask at the start of your next project
#14Managers are great at talking the talk, but it takes great developers to walk the walk. My current project is successful in spite of a similar list that was created at the inception. Over the course of 3 years, the why, the pitch, the NOT list, the Yes list, the priorities and what not have been changed and we keep afloat just because of two things : robust architecture and continues refactoring