#1: I am not my code
For developers that put their "all" into their work, it's important to let them know that if there is a problem with the product, it's not a reflection of their individuality. The work is a team effort and everyone plays a role. You know you are successful at this, if people are asking for help, and others are stepping up to help out.
#2: The mind is amazing. It automatically adjusts the road rules to justify what we do
Everyone on the team processes information differently, so it's important to learn from each other. It's exactly why the end product might just be better than anything one person could ever think of. Use that to think creatively and build smarter solutions. Challenge ideas, but be prepared to give support to the reigning choice.
Everyone on the team processes information differently, so it's important to learn from each other. It's exactly why the end product might just be better than anything one person could ever think of. Use that to think creatively and build smarter solutions. Challenge ideas, but be prepared to give support to the reigning choice.
#3: As Business Analysts, it is our job to DO the hard and discern the impossible
I've always taken the approach that the BA is the Administrative Assistant to the project team. If something isn't getting done, no matter how hard or tedious, the BA should get it done. If it can't be done, then find a workaround or make the case to take a new direction.
I've always taken the approach that the BA is the Administrative Assistant to the project team. If something isn't getting done, no matter how hard or tedious, the BA should get it done. If it can't be done, then find a workaround or make the case to take a new direction.
#4: Habit is "read only" memory
For me, it's a talent to know when to use best practices and when to break out and make a change to processes.
#5: There is always someone smarter than yourself
Regardless of industry, everything changes and it's important to stay in touch with others who may know more. Read the industry magazines and web sites, and talk to other people.
#6: Garbage in, garbage out
Product quality is directly related to the raw materials used in development. Strive to use the highest quality components and data possible. Every company tolerates different levels of quality, so make sure you understand what those thresholds are before trying to implement quality assurance practices that are too far above those quality measures.
#7: I accept that I will make mistakes, but commit to learning from them
Mistakes are a waste only if you don't learn from them. I've even been known to "take the hit" for a developer who did something wrong, admitted to it, and took accountability for it. I protected them, maintaining their anonymity, just to ensure that we move forward for the team.
#8: The only constant is change
The Business Analyst should always keep an eye out for possible changes and be ready to provide analysis of the impact to the project(s) or product(s). Make sure that all the relevant information is ready for leaders to make an educated decision.
#9: Treat those who know less than you with respect, deference, and patience.
If you have newbies on the team, make sure that their questions are answered, so that they can grow their knowledge. Often, I've seen those newbies ask great questions that end up taking the solution in a new direction. So, don't discount them if they haven't yet found the boundaries. They may pull out a gem that could be used.
#10: True authority stems from knowledge, not from position
On a high performing team, everyone is an equal, and feels like they have a voice.
