My StickyMinds.com column, Do You Need Titled Architects for Your Programs? is up. Please do comment over there.
-
RSS
-
Subscribe with Feedblitz
Search Managing Product Development
Sign up for Johanna's Pragmatic Manager email Newsletter
Email Marketing by iContactCategories
Archives
-
Johanna’s Books
Tag Cloud
agile agile architecture AYE conference Behind Closed Doors capacity change collaboration conference context estimation feedback geographically distributed teams inch pebble iterative planning kanban leadership lean lifecycle Manage It management management myth Manage Your Project Portfolio meetings multitasking one-on-one pairing Pragmatic Manager product development productivity program management project project management project portfolio project portfolio management project success project team release criteria risk team technical debt testing timebox transition to agile transparency workshop
Hi Johanna – the StickyMinds link goes to your previous blog post! Cheers, Bob.
Bob, thank you! Now fixed. Phew! — Johanna
> Even with my advocacy for architects on large programs, I am not
> suggesting a separate architecture team—I am suggesting architects
> embedded on feature teams, who do the hard work of making features
> function, refactoring, and living with the architecture and the code
> they build.
This should be coined as the 1st law of software architecture.
Great article!