A to Z Software Development Roles

Search This Blog

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.

"S" for Scrum Master. Software Development Roles: A to Z

A Scrum Master is a servant leader and facilitator for an agile development team. They ensure the Scrum framework is followed, enabling the team to maximise its efficiency and effectiveness. Scrum Masters coach the team on Agile principles and practices, helping them to self-organise and make decisions collaboratively.

Personal Story: I have been a Scrum Master for several teams. One thing I love is educating people new to the Scrum framework. One method I use involves the office kitchen. Imagine the product backlog as four different drinks: a cup of tea, a latte, a glass of water, and a long black. Sounds simple, right? However, without acceptance criteria, the team quickly learns that the drinks made aren't what the end user wanted! The first tea made: "Why is there a tea bag in my tea?" The first latte: "I wanted oat milk!" This hands-on experience helps illustrate the importance of clear acceptance criteria and continuous learning.

Interesting Fact: The Scrum framework was formalised in the early 1990s, drawing inspiration from empirical process control theory and lean manufacturing principles. It was visually likened to a rugby scrum, with the team moving as one down the field.



Popular Posts