My live blogged notes from Jason Rimmer's session at DevLearn. Forgive any typos and incoherencies.
"eLearning is a Technology Solution." ~ Trina Rimmer
Tech: code, defects, platform, tools
Solutions: stakeholders, subject matter experts, schedules
Focus on what you need to do, not how you're going to get there.
Evolve your process alongside capabilities. How do we evolve the way we work to the rapidly changing tools and tech?
1. Establish project ground rules
2. Track everything
3. Flex your process
The less you have to focus on, the faster you can do it. Flex your process to deliver your projects better. Understand WHERE your process is holding you back. Can you cut the work down into smaller chunks? You'll deliver the project more quickly. Your stakeholders will see more product more quickly.
4. Save your history -- keep versions (your customer might like the last version better than the next one..)
5. Use the right tool
6. Oops -- I missed this one :)
7. Focus on the MVP -- the minimally viable product
8. Make testing repeatable
Don't just wander around and click on things. Make a repeatable plan. Know all your possible use cases. Document that test plan and then re-run it.
9. Keep stakeholders on the team
Your stakeholders are as much a part of your team as your execution guys are. It's critical for your project being successful overall.
Let your stakeholders meet the project team. So they have confidence that things are happening. It makes them feel good. Give them visibility into what you're doing.
10. Bounding for the win
Act --> Move --> Evaluate
Always be moving. When you don't deliver, the team starts to go into a death spiral. Focus on acting, moving, evaluating. Management sees movement. You're "bounding." Smart people are always moving forward. You can't move without evaluation. "Don't get bogged down by that, make some small progress."
Always move forward, even if it's just a small amount.