I’ve been a Software Engineering Manager or Team Lead for a long time, and Agile coaching has been part of all of those jobs. I’m on the Board of Agile New England, and have been for about 10 years. I’ve been supporting the Agile community for about 13 years. Having helped multiple companies with their agility, I also have a feel for what works in specific situations, and a pragmatic approach to what and how implement it.
I enjoy management, but after speaking to some Agile Coaches I know well, I am looking to for Technical Agile Coaching positions instead. They both focus on something I am passionate about, which is focusing on the effectiveness and happiness of the entire team. They’re just going at it from different angles.Continue reading
I ended up talking about knowledge management quite a bit at Agile Games 2018 and Mob Programming 2018. I don’t have a lot of formal training in this area, but it’s something that I’ve focused on a lot, and I’ve learned a lot from people who have studied it a great deal. Rather than respond directly, I decided to add a blog post about it, to benefit more people. This is an unordered list of these tips. I would love to hear your additions or feedback on it.
Push vs Pull Communication Channels
There are two different general ways of communicating information: Push and Pull. Push is when you send information out to recipients and they get notified (email, Twitter, Slack, etc) and Pull is when the recipient seeks out that information that was published earlier (Website, wiki, CMS, documentation). Using the wrong type can prevent the recipients from having the most recent information in a timely manner. The main deciding factor is, is it more important that people know about this information as soon as possible (changes to policy, status/availability updates, issues), or that people have the information when they need it (requirements, specifications, resources, environment details). Many tools can do both, like wikis, which allow people to get notified of updates). Email doesn’t work nearly as well as you would think at either push or pull, because most people in technical fields get so many emails that they find it hard to both notice and respond to timely emails and categorize those emails so they can find them later.Continue reading
I am looking for Software Engineering Manager position in the Boston area, leading a team of (preferably) Java developers in an Agile environment. My strengths are my diversity and depth of experience, perseverance, ability to learn new technologies quickly, and communication and organizational skills. I’m happiest when I’m collaborating on hard problems, mentoring others, establishing best practices, and improving software. I’m a strong believer in the Agile philosophies and principles, and valuing quality and teamwork.
If you are looking for someone like me, or know someone who is, please contact me at firstname.lastname@example.org.
As a creative person (and as a geek), when building something (software or hardware), I often say to myself “For just a little more time and/or effort, I can add this cool feature.” There are many good reasons why this is a bad idea. I would like to lead with the reason that has caused my blog to be stagnant for months, which is that doing more than you have to gets in the way of actually finishing. An artist I almost knew once said “The hard part about painting, is not the painting, but knowing when to stop.”
Since my last post, I’ve started about six posts that I never finished because I just wanted to add this one last point, or tweak that paragraph one more time. The result was no visible work output, which is inexcusable for an Agilista.Continue reading
Last week I started my new job as a Principal Software Engineer at Workscape. I’m back in another Agile position, working on Java (and starting work on Flex, too), which are the two things I was looking for. I would have settled for a position at a company that wasn’t Agile, but it would have been hard, knowing the benefits of it. I was waiting to post this until I got my first paycheck or did my first commit of fixed issues, whichever came first. Thursday and Friday I fixed three issues, so now it’s official.
Workscape offers HR services to other companies and their employees.
I am no longer at Litle & Co. My separation agreement prevents me from discussing the details, but it’s fair to say I’m not very happy about it.
I have been a hands-on Manager, a Team Lead, and a Principal Software Engineer. I’m looking for a full-time position in the Greater Boston area (but not downtown Boston) developing Java, preferably in an Agile environment. I have extensive experience in software design and development, as well as hands-on management. My strengths are my diversity and depth of experience, perseverance, ability to learn new technologies quickly, and organizational skills. My specialty is cross-platform development and tools.
You can read more about my skills and projects, and download my resume, on my portfolio page.