Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Architecting the Agile Career


Published on

1 Part Technical
2 Parts Professional development
Splash of Humor

In this presentation we discuss the similarities between architecting a datacenter and architecting your career based on solid design principles.

Published in: Technology
  • Login to see the comments

Architecting the Agile Career

  1. 1. Architecting the Agile Career
  2. 2. @josh_atwell #CIVMUG
  3. 3. Design Principles The things that must be considered for any good design. • Requirements • Constraints • Assumptions • Risks
  4. 4. Requirements Design condition that must be satisfied • Location of Job • % Willing to Travel • Full-Time or Contract • Company Size • Benefits
  5. 5. Constraints Non-Negotiable design condition • Minimum Salary • Specific Benefits • Quantity Paid Vacation • Flexible Hours
  6. 6. Assumptions Design conditions that are accepted as true without necessarily being able to verify condition • Culture Compatibility • Duties will be as described • Resources required will be available
  7. 7. Risks Things that could prevent the success of the design • Dislike the work • Poor Management • Poor culture
  8. 8. Pick Your End Goals If you won the lottery tomorrow. How would you spend your time? If you had unlimited funds/resources how would you meet your architecture goals?
  9. 9. Pick Your End Goals What’s the best case end state? KNOW YOUR DESTINATION
  10. 10. Pick Your Path Do not think or plan strictly linearly. You have NO way of knowing all of the paths to your goals. New technologies or requirements will present themselves will require flexibility in your architecture.
  11. 11. Pick Your Path Rome was not built in a day BE FLEXIBLE. BE AGILE.
  12. 12. Skills Gap Do not fixate on a particular job. Instead focus on improving your skills. New technologies often mean new skills.
  13. 13. Skills Gap It’s not about the job. It’s about having the skills to do it. Always Growing
  14. 14. Balance Build skills that meet your professional AND personal goals. Design for High Availability
  15. 15. Balance A stable architecture is a balanced architecture. Be Tolerant of Imbalance
  16. 16. Find a Mentor Find someone in a position that interests you and let them help guide you through their experience. No need to design alone. Peer reviews. Peer reviews. Peer reviews.
  17. 17. Find a Mentor Every architecture should be reviewed by others. Get Feedback Early & Often
  18. 18. Understand the Design If you sat beside a hiring manager on a plane could you make them interested in you? If you were asked by your leadership, could you explain the value of the design?
  19. 19. Understand the Design Be able to articulate the core of your design in a 3- 5 min conversation. Know What You’re Trying to Achieve
  20. 20. Maintain Order Keep your personal affairs in order and a priority. Documentation and operability are critical in a successful design.
  21. 21. Maintain Order Good design incorporates operational considerations. Buses are CLEARLY After IT People
  22. 22. Have a Plan • Know where you want to go • Be introspective • Be Honest • Re-evaluate often
  23. 23. @josh_atwell