Roles and titles can vary between companies, there are nuances and differences. Large IT departments include additional roles that are more specific, such as database administrator, networking engineer, security engineer, project manager, or scrum master. Depending on the size and scope, a team may need more than one person for each role. At smaller organizations, like ours, there is more overlap between the roles. Let’s introduce you to the team!
Related Titles: Product Owner, Business Analyst, Software Analyst
Related Titles: Interface Designer, User Researcher
Related Titles: Engineer in Test, Quality Control
Related Titles: Mobile Developer
Related Titles: Front-end Developer, Programmer, Web Engineer
There are subtle differences between engineers and developers, but for the sake of this course, you can think of them as the same.
At Poodle Jumper, we leverage the lean development methodology because it allows us to quickly iterate while controlling development costs. An iteration is when we repeat the process for an idea, design, or product until it is ready.
Our software development team is responsible for the design, development, and testing of our website and two iOS mobile apps. The team includes a product manager, a user experience designer, a quality assurance engineer, a web developer, an iOS developer, and a software engineer.
The Product Manager organizes the ideas into a list, called the backlog, and leverages their productivity skill to ensure the priorities are aligned with the strategy.
The User Experience Designer leverages their innovation skill to brainstorm new ideas for solving problems with the team. They create sketches of what a solution could feel like and test the idea with potential customers. The team leverages their communication skills as they review the idea, identify risks or issues, and define what to build. When the team has an agreement on the direction, the engineers design the architecture for how the software will work.
The Quality Assurance Engineer outlines tests to ensure the software will work as needed and drive the expected results.
The iOS Engineer collaborates with the User Experience Designer to create storyboards that lay out the screens and identify what data elements the feature will need.
The Software Engineer creates the database elements needed and writes the logic in server-side code. When the code is ready, the team reviews it together to make sure it matches what they set out to build.
The Web Developer creates the features for the website and writes web services to connect everything together.
The Quality Assurance Engineer executes their tests and shares the results. The team meets to review the results and decide if the feature is ready to be released to users.
When the MVP is released, the team learns from the analytics, user feedback, and reported issues. Insights from the learnings are captured as ideas and the team leverages their agility skill to embrace the changes and adapt the feature as needed in the next iteration.
In the next section, we’ll take a deeper dive into the roles to show you what their jobs look like on a day-to-day basis.