Soft Skills and Proficiencies:
● Knowledge of basic IT skills and industry terminology
● Google Suite (Google Chat, Google Drive, Google Documents, and Gmail)
● Basic system requirements identification and documentation analysis
● Good command of application domain knowledge
● A good understanding of the development lifecycle
● Project Management experience
● Familiarity with Agile and Waterfall methodologies
● Knowledge of Scrum and Kanban
● Ability to plan, design, and analyze user requirements for development and/or support
● The ability to explain possible risks to and maintain communication with the team
● Excellent problem solving, time management, and analytical skills
● Adaptive and proactive spirit
● Open-mindedness and the ability to be trained
Responsibilities:
● Interpret client concepts to make clear specifications that direct the software development team
● Define functional and quality requirements to allow project managers to design and build the
product, and allow testers to verify
● Analyze requirements to make sure they aren’t too vague, ambiguous, or confusing; determining
if more detail is required for developers to do their jobs
● Write requirements so that all stakeholders have an organizational structure from which to work
● Create analytical models to represent graphical requirements, processes, and flows; determining
the best way to communicate non-textual requirements
● Validate and manage the good maintenance of all client requirements by tracking information
● Facilitate priorities by analyzing the project scope and client objectives, making sure everyone
has the right information to make the right decisions
● This role also supports and develops all team members involved in projects, by recognizing the
need for: Eliminating distractions
● Understanding different points of view and acting as a neutral facilitator between workgroups
● Reading between the lines to make sure all views are vocalized
● Asking pointed questions to help break down miscommunication
● Observing subtleties that users may not mention
● Identifying and clarifying unspoken assumptions, analyzing the difference between “wants” and
“needs”
● Improving communication by understanding different styles of collaboration; recognizing other
group members’ limitations based on skills, time zones, workloads, culture, etc.