A to Z Software Development Roles

I’m Chris Saunders, a technologist passionate about product delivery and innovation in the technology industry. This blog is where I share my insights, experiences, and ideas around building and delivering exceptional products.

Software Development Roles: Skill Attributes Visualisation

This 3D scatter plot visualises various software development roles based on three key skill attributes:

  • Project Timeline (x-axis): Representing the spectrum from project start to project end.
  • Focus Orientation (y-axis): Spanning from people focused to technology focused roles.
  • Thinking Style (z-axis): Differentiating between operational thinking and strategic thinking.

Each marker represents a distinct role, with its position indicating the relative emphasis on each of these attributes. Use the chart to explore how different roles balance these skills. How one person in a 3D space could assume another role nearby in the space.

Click the "Reset Chart View" button to reset the chart to its default view.

Click the "Set Y and X Front View" button to set the chart to see Y on the left and X on the bottom.

Click the "Set Y and Z Front View" button to set the chart to see Y on the left and Z on the bottom.

Interacting with the 3D Scatter Plot:

Zoom:

  • Mouse Scroll: Scroll the mouse wheel up and down to zoom in and out.

Rotate:

  • Click and Drag: Click and drag on the plot to rotate it in any direction.
  • Right Click and Drag: Right-click and drag on the plot to pan it left, right, up, or down.

Reset Chart View:

  • Reset Button: Click the "Reset Chart View" button below the plot to reset the view to its default position (Y axis left, X axis bottom, and Z axis depth).

Explore:

  • Hover: Hover over a data point to see additional information about the role it represents.

"P" for Product Owner. Software Development Roles: A to Z

The Product Owner plays a pivotal role in agile development, defining and prioritising the product backlog to maximise team value delivery. They act as a crucial bridge between stakeholders and the development team, translating business needs into actionable user stories and acceptance criteria.

Personal Story: In my role as a Product Owner, I delegate defect and business-as-usual work items to the team, ensuring these tasks are managed within an agreed percentage of the total workload, typically around 30%. I also enjoy introducing experimental work items into the backlog. Each experiment has a clear hypothesis and defined success criteria, enabling data-driven decision-making.

Interesting Fact: The "owner" in Product Owner signifies the leadership, decision-making authority, and responsibility held over the product’s direction and success, rather than implying legal ownership.



By

Popular Posts