12 Jun 2012
We recently switched issue trackers—and while a feat in and of itself—half the battle was getting our arms wrapped around the replacement… JIRA. When discussing the topic with one of our clients they remarked, “JIRA gives you sooooo much rope, it’s almost impossible not to hang yourself with it all!”
13 Apr 2012
D^5 was built on Agile concepts. It’s centered around individuals and interactions: It’s centered around working software: It’s centered around customer collaboration: And it’s centered around responding (not reacting) to change.
12 Apr 2012
I think it’s important to point out at this stage that we used the D^5 process to create… the D^5 process. We used D^5 to sequence and organize this series of blog posts (look at the titles and order).
11 Apr 2012
With questions answered, ideas sketched and everyone sick of me asking, “why?”—I moved to developing D^5.
10 Apr 2012
Interviews complete, and all of my dog-eared project management books referenced; I was ready to start designing D^5. I started where I often do—flow-charting.
5 Apr 2012
As my bio indicates, this software business was entirely new to me. I dabbled with web apps in the past, created a handful of websites, and managed — from a very, very high-level — a few web projects. But my experience is in the much more progressive-sequence world of construction, manufacturing, and marketing. These are industries with well-defined, industry standard work-flows.
Part of the draw to the web studio was the unknown.
3 Apr 2012
Recently we deployed our new work process called D^5. It’s a five step program. Like most five step programs, its initiation started by admitting we had a problem.
Have a project that needs help?