THIS IS THE DAWNING OF THE AGE OF ASPARAGUS – WE’RE BUILDING WHAT?

I have worked with companies of all sizes across a variety of products on various platforms.   Here are some common mistakes that companies make from the outset that increase the likelihood of a project going sideways.

“Let’s Be Lean/Agile”
Going with a lean or agile approach does not mean throw all documentation and meetings out the window and just build it.  It is a framework that encourages scaling process to fit the needs of the project, and having the inherent ability to adapt to change in a minimally disruptive manner.  If anything, adopting this approach increases the need for clear documentation including goals, priorities, dependencies, checkpoints, and acceptance criteria.  I’ve used post-its, whiteboards, wikis, and 50+ page specifications depending on the project.  Use the medium that makes sense, but the important thing is to capture the information and check progress frequently.

“Let’s Just Get in a Room and Work it Out”
I’ve had awesome whiteboard sessions where brilliant minds have come together to solve a problem only to overhear five minutes later “That’s a great solution, but that’s not the problem we’re solving for.”  Brainstorming sessions are a great tool, but they are not a replacement for understanding the goals and problems you are attempting to solve.

• Understand the problem – if you’re not sure what you’re solving for, come back later.
• Stay focused – if it’s not directly adding value, it’s gilding.
• Mirror back what is being decided to make sure everyone has the same understanding.
• Make a sketch and capture the image.
• Write it down – assign owners and next steps.

​“Let’s Have a Project Kickoff”
Yes!  Do have a project kickoff.  A project kickoff is a great opportunity to bring the project team together to present the project, answer questions, and bring everyone on board.  Make sure your project kickoff is effective and not just an excuse for a pizza party.

• Prepare for the meeting!
• Define the purpose, goals, and audience for the project.
• Analyze and prioritize features and tasks.
• Don’t overlook usability and accessibility.
• Step back and look at why you are doing the project in the first place.
• Assess your resource and technology needs.
• Understand external factors that affect your project.
• Make participants invested by assigning ownership.
• Leave time for discussion, but keep the discussion productive.
• Take notes and post them immediately after the kickoff.
• Capture decisions and action items including a single owner and due dates.
• Follow up!

Whether your team is 3 or 30 people, don’t fall into the trap of thinking you can wing it.  Spending a little time upfront to think about what you’re building and aligning resources will save a lot of aggravation in the home stretch.