Manage your career like a project—Finding a Project Manager mentor

Wow- thanks for the response to my post on “the accidental PM”!  I have received several inquiries about other job titles and how they should handle their career—I will definitely address this interesting topic again, soon. 

I know many lead developers, code jockeys, business analysts and other members of development teams that are often assigned to projects with little or no say in the process. A project manager needs your skill set and specifically requested you or you are assigned from resource management or the PMO. However, it is in your best interest to be proactive in the process by making your preferences known.

First things first. The time to think about your career is not after an assignment is made and you are stuck on a project –especially if you are being sent to a multi-year project. Rather, you need to look at where you want to be and what you want to be doing in three to five years. You may enjoy coding, QA, business analysis, architecture, or systems. Not everyone wants or needs to be a project manager or operational vice-president.

In the beginning of your career, your knowledge of the profession needs to mature. Even though you have academic training in the field and perhaps internships that added real world knowledge, the world of work is different from academic or intern assignments. So, in the initial stages of working for a living—say the first three years—you should focus on learning to work effectively on a team, meeting management expectations, and understanding the organization.

The first three years of work is the time to collect data. Beyond the project on which you are working, talk with people working on different projects about their tasks and management. It may be necessary for you to create opportunities to get to know people on other project teams. If you enjoy sports, think about joining the softball team or working out in the corporate exercise facilities. Alternatively, volunteer for an internal project that supports company community goals. File the bits of shared experiential information for future use.

After a couple years of working, conduct your own critical analysis of your skills and interests. Find capabilities that you want or need to improve. Look at tasks you enjoyed doing and excelled at and ones that were drudgery. Consider changes in your personal situation in terms of time you want to commit to your career and other obligations that may have occurred since you began work—like marriage and children. If you heard about individuals within your organization that others enjoyed working with, learning from, or just admired keep those individuals in mind when creating your career plan.

When your current assignment is within six months of completion, it is time to act for your future. Put together either formally or informally, a list of preferences for your next assignment. If there is a project you really want to work on or a manager or senior technical specialist you want to learn from, now is the time to make that preference known to the decision makers in your organization. Either schedule a meeting with those who decide your fate or as part of your annual performance review, state your preferences for future assignments and the reasons for them.

Let the decision makers know what you are doing in preparation for your preferred next assignment. Ask for their help and suggestions. Companies want happy, productive employees and it is in your best interest to tell them how to help you become the type of employee they need.

Practice patience. You may not get the ideal assignment the first time you try. However, managing your career is your job and sometimes—but not always—companies and managers remember those who stepped up for corporate priorities. However, do not give up if you do not get what you want at first. Continue to push in the direction you want your career to go.

Project Management and the Agility Factor

Agility is such a positive sounding word. In common usage, agility is synonymous with quickness, lightness, ease of movement, nimbleness—beautiful gymnasts are agile, great basketball players are agile—I feel  buoyant just talking about it (Wish my march madness team picks had showed more agility!)

Agility in terms of software development is an approach that addresses rapid change—in requirements or market places or technology.  Business has labeled agility through terms like just in time, shortened life cycles, and customer driven.  It goes by many names in the software world: lean or extreme (XP) programming, feature-driven development, and Scrum.

As described by Alistair Cockburn (a signee to the original Agile Manifesto) in “Agile software development: the business of innovation”, agile approaches have short iterations—two- to six-weeks. Development teams make constant trade-offs and practice dynamic prioritization, which allows a customer to reprioritize the “features desired in the next cycle, discarding originally planned features and adding new ones.”

According to the Agile Manifesto, projects and project managers must emphasize:

  • Individuals and interactions over processes and tools
  • Working software over comprehensive documentation
  • Customer collaboration over contract negotiation
  • Responding to change over following a plan

Not all developers work well under the expectations of agile development. Because of the short cycle times, there is a much greater need for constant communication, cooperative work relationships, and strong technical skills.

How Can Project Managers Promote Agility in Their Organization?

  1. Get people working together into close physical proximity.  This is not always possible- just preferred.
  2. Discourage formal communications such as reports and emails and encourage face-to-face meetings or video conferencing if players are not co-located.
  3. Build individual competencies.
  4. Use tools to support interaction.
  5. Select team members who enjoy working collaboratively rather than alone.
  6. Have frequent—even daily—quick team meetings (10 to 15 minutes) to discuss what was done yesterday and planned for today.
  7. Integrate testing into development and consider using automatic testing tools—this is as opposed to the process of finishing a build and then turning it over to QA or test.
  8. Ensure active user participation.
  9. Keep teams small. Not tiny- just small.
  10. Select team members with diversity of experience and approaches to solving problems.
  11. Monitor the development and the work environment frequently to detect unexpected occurrences before they become problems.
  12. Create empathetic management—people respond more positively and recover from all kinds of trauma when they encounter empathy. Changing methodology from traditional development process to agile development is a big change to a project or an organization—it can be traumatic. In addition to leading people through this with resilience, management must also be empathetic to the impact of the change.
  13. Leverage human complexity—support learning about the people on your team—not just their technical prowess, but also their interests, personality types/characteristics. Promote self-knowledge, creative expression, and shared knowledge with teammates. Deep understanding enhances creativity, which is essential for acting when there is little time to prepare.
  14. Encourage mentoring—constant change and shifting priorities can render even professionals less effective. Mentoring provides guidance and support and helps build relationships. Readiness for change and adaptability can be improved by mentoring.
  15. Tap into community building efforts, such as communities of practice.

Do you see differences in the capability and personality needs of agile projects? Please share your experiences, comments, and suggestions.  And what about the new concept being proposed called “Agile Project Management”?  Do you think this will take hold?  What is agile project management?

Follow

Get every new post delivered to your Inbox.

Join 383 other followers