Ionel Condor - Lessons Learned in Agile Career Development

2,757 views

Published on

Published in: Business, Technology
  • wrong formatting here after the upload, so pls use this one:
    http://www.slideshare.net/ionelc/lessons-learned-in-agile-career-development-jazoon-2012-14051041
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here

Ionel Condor - Lessons Learned in Agile Career Development

  1. 1. Agenda• About me• The story• Career Development – where we are, how we arrived here• Setting the stage for Career Development• A model of learning• Dilemmas and false friends along the way• Examples, examples, more 2 examples Learned in AgileLessons4/5/2012 Ionel Condor – Career Development
  2. 2. About me• Started to work in 1998 as a Jr Developer• Continued my Dev Career as Sr Dev, later as a Lead• Switched to a Jr Project Manager position and later Jr Dev Manager• Continued as a Mid Dev Manager …and the journey continues…(to a Sr Manager?, back to Dev?, back to Project Management?) Ionel Condor – Lessons• Married, 1 daughterAgile Career4/5/2012 Learned in Development
  3. 3. The storySource: http://getcareerlinks.blogspot.co.uk
  4. 4. Career Development – where we are, how we arrived here• No career development; we pay you to work• It’s not my job as your Manager, better ask HR ….• Yes, but only on soft skills; technical career? …you have Internet and you have free Condor – Lessons Ionel Learned in Agile Career Development
  5. 5. Career Development – where we are, how we arrived here • Individual or group pattern career plan, but no one to measure and give feedback and follow up • “We are Agile, so you need to be Agile ”… No more Career Paths (see Craig Larman) • “There Is No Career Ladder” – a recent HBR • “Career Plans Are Dangerous” – an even more recent HBR Ionel Condor – Lessons4/5/2012 Learned in Agile Career Development
  6. 6. Setting the stage for Career Development Ionel Condor – Lessons4/5/2012 Learned in Agile Career Development
  7. 7. Setting the stage for Career DevelopmentFactors for Inhibitors:success: • Lack of belief • Drive & in self Passion • Fear of Risk • Leadership • Poor • Networking Communication • Integrity • Procrastinatio • Luck & n Timing • Lack of • Intellect passion • Taking risks • Greed and ego • Planning
  8. 8. A model of learningDreyfus modelA model of skill acquisition Expert Needs to be Proficient put in a Needs context that Competent unhindered favors his Needs real practice and intuition and Advanced the big world creativity Beginner exposure, Pro generalNovice Needs cess Oriented picture, simple, contro SystemNeeds lled Orientedrecipes simulations, monitoringand firstsuccesses Ionel Condor – Lessons4/5/2012 Learned in Agile Career Development
  9. 9. So you want to be an expert…BAD NEWSYou need to budget 10 years of effort in thesame subject areaAND practice in an environment where:- Tasks are well defined (for your level of expertise)- Tasks are challenging & doable- The environment (context) gives you feedback that you can use- The environment provides opportunities for repetition and correctionGOOD NEWSOnce you become an expert in one field, it
  10. 10. Recommendations for Developers/Testers1. Winners do not carry losers2. Keep practice: “if you think you are standing firm, be careful that you dont fall!”3. Watch out: Most people are and will remain as AdvancedBeginners4. Skills and abilities we constantly use/practice will begin todominate and more of our brain will become wired for thesepurposes5. “use it or loose it”: want to be a better task estimator? Practicemore task estimations and retrospectives
  11. 11. Recommendations for Managers1. Favor rules for Novices and Intuition plus Creativity forExperts2. Do not create general rules and ask the experts to follow them, so do not alienate experienced practitioners in favor of novices3. There is no substitute (rule, tool, standard,methodology) for thinking and communication
  12. 12. A model of learningSource: http://www.coderfriendly.com Ionel Condor – Lessons 4/5/2012 Learned in Agile Career Development
  13. 13. Dilemmas and false friends along the way• specialist/generalist• architect/manager/project manager/business roles• Peter’s principle• layer vs feature• career aspirations vs skills forecasting• career path anti patterns: sheep dip, time constraints, lack of smart objectives, lack of coaches and mentors, inadequate learning, inadequate reading, memory/brain bugs , risk vs Ionel Condor – Lessons benefits4/5/2012 Learned in Agile Career Development
  14. 14. Examples, examples Ionel Condor – Lessons4/5/2012 Learned in Agile Career Development
  15. 15. Examples, examples Ionel Condor – Lessons4/5/2012 Learned in Agile Career Development
  16. 16. Accountability and metrics Ionel Condor – Lessons4/5/2012 Learned in Agile Career Development
  17. 17. Accountability and metrics
  18. 18. Accountability and metrics• Does your company offer you also the time to study ? Should it ? – Monday morning we work, but the project is called “Career Plan” – Friday in the afternoon we work, but the project is called “Ad- hoc presentations”• Are you doing your part ? 40-20
  19. 19. Accountability and• metrics Every day: thousands of new books available to our Engineers, practically we can provide anything they ask for their training, in a legal way• New hire: assign a coach and encourage to find a mentor• Weekly: Study group/self-study every Monday morning; mandatory• Weekly: Self study or open sessions (ad-hoc subjects) every Friday evening• Weekly: Group of ….• Monthly: Technical presentations – tech & findings in our projects• Monthly: Enlightening talk and a session of pair programming (usually one of the Monday morning)• 3- 6 months: Review all our career plans, re-evaluate, re-start• 3-6 months: Identify/review key areas where we need to grow our staff, on both Generalist path and Specialist path• 6-12 months: Identify Coaches in each area (es. Performance testing, UI Dev, Messaging, etc, etc)• Yearly: Certification plan & Fundamental skills for Jr/Mids• Yearly: Grow tech skills for Mid/Sr/leads – conferences, leadership trainings• Decide & Inspect & Adapt
  20. 20. Recomandations• Books• Podcasts• User Groups• Public or Private/In house Conferences• RSS Readers for Blogs• Group study / group presentations / group practice• Daily Code Kata s
  21. 21. Some bookrecommendations Change Management Being effective in attaining goals Good teams
  22. 22. Some bookrecommendations move that tasks out of the your mind by recording it externally Good Development Style never gets old The big picture of Software Development
  23. 23. Some bookrecommendations Description of a complete job life cycle Good practices never gets old A masterpiece !!! A must read !!!
  24. 24. Some bookrecommendations A strategy for planning and creating a successful life in software development How they work Samples of elegant solutions
  25. 25. Some bookrecommendations Attitudes and techniques of a software craftsmanship Back to the basics  Wisdom from relevant people
  26. 26. Some bookrecommendations If you have need of changing your organization How to prioritize, organize and act Learn how the brain learns and learn how to learn
  27. 27. Some bookrecommendations Technical wisdom A good one to read in a vacation with plenty of time If you are no more an apprentice then you will learn how to be a master and validate your advices according to this book
  28. 28. Some bookrecommendations So you decided to move to management …OK, this is the first book you need to read How brain works and why you need to sleep …for general audience If you feel you need and can change your org but not sure about the patterns
  29. 29. Some bookrecommendations The right skills in the right place at the right time
  30. 30. Some bookrecommendations Interviews with Experts
  31. 31. A Good Career
  32. 32. Blog:http://ionelcondor.wordpress.com/Twitter:@ionel_condorhttps://twitter.com/Thank you!#!/ionel_condor
  33. 33. Conditions ofuse Conditions of useYou can use this template With the use of this free template you accept thefor your personal, following use and license conditions.educational and business You are free:presentations. To Share — to copy, distribute and transmit the work Under the following conditions: Attribution — You must attribute the work in the manner specified by the author or licensor (but not in any way that suggests that they endorse you or your use of the work). No Derivative Works — You may not alter, transform, or build upon this work. In no event shall Showeet.com be liable for any indirect, special or consequential damages arising out of or in connection with the use of the template, diagram or map. Your text here 34 http://www.showeet.com http://creativecommons.org/licenses/by-nd/3.0/ Date

×