Ever had a great idea and needed a place to store it? Oh wait, you already have an app for that called Evernote. Wait, stay with us here. This tool that we found may just help you “visualize” your ideas in once central place and collaborate with other people about your ideas.
Enter: Wridea – Idea Management and Brainstorming Tools
As we look towards this year with anticipation I see that my clients have a ton of work ahead of them. Certainly it’s easy to get tunnel-vision, in that we have mission critical projects and focus solely on them.
Bottom line: we need to get them done.
But we need not forget our drive for continuous improvement and refactoring! Some things that have come to mind for me as we get steeped into our projects include:
Evolving the current processes – Ask the question: “What can be changed?”
Monitoring our current health with empirical skepticism – “Does this make sense?”
Having a beginner’s mind and avoid the expert-attitude. – “Why are we doing this?”
These questions may be broad, but they also are good starting points for improving our processes. Keep a fresh perspective for the new year!
2010 has been a fantastic year. We’ve grown massively and have completed a lot of our 2010 goals. So what’s next?
2011 – We’re going to be launching some really cool initiatives and there are some very interesting partnerships brewing that will position us to better serve the Agile community in the months and years to come. Get excited. We certainly are.
A couple of hints:
Think “Continuing Education”
Yep. All these are brewing. Stewing. Boiling. Here’s to a great 2011!!!
Many of our readers are consultants, coaches, and Agile software development practitioners. We can help our clients, customers, and companies where we are, face-to-face.
Why not use online mediums to broaden our audience? We know that @pmstudent runs his own show on his site pmstudent.com and that works for him, but what about the rest of us? Ever wanted to set up your own class? How about your own University?
To remove impediments of the Scrum team and the owner of the process.
We wrote a post on how a ScrumMaster can help out with communication here. Seems simple enough right? But with so many stories around how teams using Scrum are failing left and right, what could be some possible ways that a ScrumMaster can help their team out by not being patient?