On my quest for Agile blogging notoriety, I am often faced with the dilemma of what to blog about and how often. Some books advise daily blogging, some weekly, though all say more is better. But who has the time? And the ideas? So how to solve this problem? I don’t think there is really one solution, just some mitigation techniques and advice I can offer. Here are some things I do to document my ideas for blogs and try and blog more frequently.
As I look back at the past year of my life, I realize how much I have learned from Agile 2012 to Agile 2013. Yes, I should be learning things every year, in fact I strive to learn every day, but in the past year I have learned exponential amounts more than in the past years of my life. I wonder if this is a phenomenon that many people realize at points in their lives, or every year? I have not just learned about Agile and gained work experience (though I have done those things) but I have also learned some huge life lessons and learned a lot about myself.
The original post is one I contributed to on Leslie J. Morse’s blog in reference to Borrowed Light and Women In Agile. it details how to share your credibility with others to build their reputation and credibility – borrowed light.
So I’ve alluded to a UX runway and my work with Agile and UX in some of my previous posts, but what does that mean? Agile has been the buzz for the past decade and UX was quick behind. First, let me give some background on UX and my role on the team.
So I’m being an Agile player. I’m dating a few different versions of Agile to see which works best while trying to keep it from the other methods I’m test driving. Don’t tell Scrum that I was scoping out Kanban. Don’t let Kanban know I made a date to get to know TDD better. How can I help the team decide which is best when there are so many options to consider?