● Don't be bashful. Analysts on the team are counting on you to tell what you know and to correct their misconceptions and oversights.
● Help the analyst to understand how your work is done. Provide a context for your remarks. Give examples.
● Ask for the features you need to do your work. Don't assume that your needs are unimportant or impossible to meet.
● Ask for the features that make your work easier, even in small ways.
● Make a distinction between features you must have and those that would be nice for you. Set priorities and make them clear to the analyst
● Do state the obvious (once, at least). Don't assume that something you know is "common knowledge."
● Ask for clarification. Don't assume that you are the only one confused. If an analyst starts talking " computerate," bring them gently back down to Earth.
● Restate the analyst's points in your own words to make sure you understand each other.
● Mention problems that you see when you see them. Don't assume problems will " get worked out later."
● Discuss needs you will have after the system is finished. Plan ahead for working independently once the analyst has gone on to other projects.
● Be open to ideas and maintain a non-judgmental stance.
Hello, my name is Jack Sparrow. I'm a 50 year old self-employed Pirate from the Caribbean.
No comments:
Post a Comment