Reduce Churn and Improve an Existing Software Development Practice

Focus on maximizing value when creating artifacts for the software development life cycle.

Unlock

This content requires an active subscription.

Access this content by logging in with your Info-Tech Research Group membership or contacting one of our representatives for assistance.

Speak With A Representative Sign In
or Call: 1-888-670-8889 (US) or 1-844-618-3192 (CAN)

Your Challenge

  • Managers have implemented Agile, but struggle to realize any significant gain from it.
  • Managers want to know what other Agile techniques exist within various development domains.
  • Managers need an analytical model through which decisions about reduction of technical debt can be realized.

Our Advice

Critical Insight

  • Development practices should focus on generating artifact value instead of processes.
  • Artifacts can devalue each other and this codependency needs to be managed through a regular assessment.
  • Inter and intra-project artifact dependencies should be accounted for in the assessment of an artifact’s value.
  • Value for an artifact is measured across two criteria: reusability and maintainability.

Impact and Result

  • Categorize artifacts within your software practice based on value and churn.
  • Quantify the cost of poor artifact management.
  • Understand the different Agile techniques for improving artifact value.
  • Create a development practice roadmap to go from where you are today into the future.

Reduce Churn and Improve an Existing Software Development Practice

1

Make the Business Case

Realize many development departments are suffering. Use this toolkit to help you improve the value of your artifacts.

2

Determine the value of development practice artifacts

Review and evaluate your current application development process.

3

Select the techniques to help improve the value of development artifacts

Evaluate the fit of all possible techniques that generate your artifact through ROI and impact analysis.

4

Rollout the Process

Prioritize your rollout based on your organization’s prioritization profile.

5

Monitor the Process

Establish metrics to track the progress and success of the amended app dev process.

Onsite Workshop

Book Your Workshop

Onsite workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn't enough, we offer low-cost onsite delivery of our project workshops. We take you through every phase of your project and ensure that you have a roadmap in place to complete your project successfully.

Module 1: Assess Your Artifacts

The Purpose

  • Understand the common development pains organizations are facing.
  • Map artifacts to specific pain points in your current app dev process.
  • Assess your artifacts based on churn and risk.

Key Benefits Achieved

  • Identify and address the gaps in your existing app dev process.
  • Determine the appropriate action for each artifact.

Activities:
Outputs

1.1

Getting started

  • List of key stakeholders

1.2

Assess your current development process

  • Assessment of current app dev process

1.3

Determine the fate of your artifacts

  • List of artifacts to be archived, modified and automated

Module 2: Select the Techniques

The Purpose

  • Understand the processes and products of several design, development, testing and deployment techniques

Key Benefits Achieved

  • Select the best fitting technique
  • Conduct an impact analysis of a technique on your existing app dev process

Activities:
Outputs

2.1

Select the design and development techniques

  • List of design and development techniques to rollout

2.2

Select the testing and deployment techniques

  • List of testing and deployment techniques to rollout

Module 3: Prepare and Execute Your Rollout

The Purpose

  • How to prioritize your rollout
  • The dev practice metrics to gauge success

Key Benefits Achieved

  • Prioritize your rollout with dependencies in mind
  • Build a communication plan with stakeholders

Activities:
Outputs

3.1

Prepare your rollout

  • Technique rollout order of execution and project dependencies mapping

3.2

Communicate with stakeholders

  • List of dev practice metrics