LASR+

LASR+ is an extension of the LASR method that introduces additional activities and steps. It can be useful if, after completing Step 4, you still lack a solid understanding of the system under review.
LASR+ includes code level checks and an organizational perspective.

Calculator
Process Diagram LASR+

Dive for Pearls

When to apply?

If the results from the LASR review appear too generic or disorganized.
If large gaps have been identified where measurements really help to evaluate (e.g. performance).

Step 5: Maturity Boost

Analytically assess and expand on previous results, like quality goals, solution approaches or risks.

What are the key tasks?

  • Organize and consolidate the results of the previous LASR steps
  • Identify and prioritize gaps in the analysis so far

Tools and practices

Informal architecture overview, solution strategy table, simple utility tree

Step 6: Tool-based Evaluation

Ensure that architectural ideas are apperent on source code level. Replace ‘gut feeling’ with reliable metrics.

What are the key tasks?

  • Match source code constructs with your structuring ideas
  • Perform specific measurements (e.g. response times, availability)

Tools and practices

Perform structure and dependency checks, static code analysis, dynamic checks (e.g. of load behavior)

Scout the Surroundings

When to apply?

If a violation of guidelines is suspected in earlier steps.
If you assume that the solution does not fit the organization’s structure or culture.

Step 7: Constraint Assessment

Ensure that the solution complies with all relevant constraints.

What are the key tasks?

  • Find and evaluate relevant constraints on business and technical side
  • Check compliance with the constraints found: Mark as OK or as violation.
  • Challenge violated constraints

Tools and practices

Stakeholder interviews, review of relevant guidelines, checklists

Step 8: Organizational Fitness-Check

Link the software solution to the structure, processes and culture of the organization.

What are the key tasks?

  • Align software structure and team structure (‘Conway’s Law’)
  • Check the suitability of the software architecture for the existing development approach, including roles and processes
  • Clarify whether the market/domain dynamics match the development dynamics

Tools and practices

Frameworks for organizational development and dynamic scaling approaches such as Team Topologies, unfix or LeSS

Learn more about LASR+

In the second part of the LASR book you find out more about the steps in the optional deep dive.

LASR Book