Adam Edgerton's Blog
Here's part # in the series explaining our "full stack" at a high level. If you missed part 1, or part 2 make sure to give those a read first. If you prefer, you can read the long-form post with all the content in one. Again, feel free to call me on any technicalities or suggest changes/additions in the comments!
Here's part 2 in the series explaining our "full stack" at a high level. If you missed part 1, make sure to give it a read first. If you prefer, you can read the long-form post with all the content in one. Again, feel free to call me on any technicalities or suggest changes/additions in the comments!
Data automation has been popular business buzzword jargon as of late, and to some extent, rightfully so! It saves time, creates seamless integration between applications, and can provide always-on, real-time information for making appropriate decisions. But data is only as good as the story it tells, and automation often hinders the storytellers that it aims to serve. Until machine learning surpasses human capabilities, there are key aspects of manual, hands-on project management that can't be effectively replaced by automation (though I'm sure some will try).
With the dust settled following the 2014 Digital PM Summit in Austin, it's time to take a moment to refelct on another year of great keynote sessions, enjoyable conversations with like-minded PMs, well-attended afterparties, and a fun host city. The event grew in size and improved on the 2013 event in many ways.
The 2014 Digital PM Summit is here! I'm greatly looking forward to presenting on organizational growth from a PM perspective. I've arrived at the final post in this mega-series supporting the presentation, which focuses on planning (or not planning) for growth. It takes a look at examples where planning is called for, while in other cases making decisions based on growing pains is the most efficient route to success.
With my presentation at the Digital PM Summit coming up on October 7th, here is post number nine in my series on organizational growth. This post makes the case that if you want documentation that has a shelf life of more than 6-12 months while growing, you need to focus on the "why" and not the "what" when creating documentation.
With my presentation at this October's Digital PM Summit just a few weeks away, here is post number eight in my series that started after I first presented on the topic of growth at Drupalcon Austin. This post investigates how to create process frameworks that hold up throughout phases of organizational growth.