Later in my career, once I became a lead developer, I learned that I now had another responsibility - deliver a project on time.
Still later, as a software architect I picked up another responsibility - to make it easier for the team of developers to be successful.
Today, I recognize another responsibility - deliver value to the business.
In the above chart, blue represents focus on Self, red is focus on the Team, and yellow is focus on the Business.What does your chart look like?
2 comments:
For sustainability, I don't believe it can be an either/or thing. In the contract project house I used to work for, we applied what we called the "three green" test to every project opportunity:
Will this be good for the team? Will it let them grow as professionals without hurting their families?
Will this be good for our company, i.e. can we execute profitably?
Will this be good for our customer, i.e. will it really deliver business value to them over time? (Also called "what would I recommend to my brother" test)
You have to succeed at all three, most of the time. And having different people advocating solely for different interests undermines collaboration and adds overhead.
Agreed, it is not either/or. That is why the colors overlap on the chart - each role still has the same total amount of responsibility, it is just split differently.
The post is about my growth as a software professional working on teams. It is observational of what I felt my responsibilities (and others' responsibilities) to be in each of the roles.
Post a Comment