You can’t build a great product if you don’t know why you are building it in the first place. How do you know what your customers really need? A good place to start is to ask them: 1. You need to have that conversation early and make sure your customers know what you’ll need to best serve them. You are defining the rules of engagement. Basic stuff.Įxpectation setting, on the other hand is about you communicating clearly with your team and stakeholders what it is going to take to make this project a success. These questions serve two goals: alignment and expectation setting.Īlignment is about making sure you and everyone else are on the same page with regard to why we are here, what we’re trying to do, and how are we going to get there. To nip this problem in the bud, when I was at ThoughtWorks we created a lightweight project chartering tool called “The Agile Inception Deck: 10 questions and exercises you’d be crazy not to ask before starting your project.” While good teams can roll with these punches and adapt as they go, it’s a form of waste that can hurt or kill the unwary before they even get out of the gate. This happens all the time on projects: assuming there is consensus when none exists. How many of your projects start off like this: You and your team get together at the start of your project thinking you are all on the same page?Īnd when you start building something, you realize you were thinking something completely different. Then you start actually building, and you realize that you all had something different in mind. As you begin the project, you and your team are all on the same page. 10 questions to ask at the start of your next project Below is a lightweight you can use to fill this gap and get your project headed in the right direction long before the first line of code every gets written. One area most agile methods are completely silent on is project chartering.
0 Comments
Leave a Reply. |