business analysis

[article]

How Businesses Stay Agile: The Art of Being Retrospective

Summary:
The greatest use for agile in business is in changing how you tackle problems and projects. Rather than defining the whole project and setting a “way forward,” an agile approach takes things much more iteratively. That means meeting as a team on a frequent and regular basis to share problems and successes, then making improvements as needed—being retrospective.

The greatest use for agile in business is in changing how you tackle problems and projects. Rather than defining the whole project and setting a “way forward,” an agile approach takes things much more iteratively. That means meeting as a team on a frequent and regular basis to share problems and successes, then making improvements as needed—being retrospective.

About the author

[article]

Testing during Transition: Test Criteria for Outsourced Software

Summary:
In the world of IT outsourcing, it is not uncommon for a company to have its applications and infrastructure developed or maintained by others. As vendors compete for this business, a common trial is testing the transition activity as a whole. How would you design acceptance criteria of a transition trial so that it is testable and clearly communicated?

In the world of IT outsourcing, it is not uncommon for a company to have its applications and infrastructure developed or maintained by others. As vendors compete for this business, a common trial is testing the transition activity as a whole. How would you design acceptance criteria of a transition trial so that it is testable and clearly communicated?

About the author

[article]

Estimating Cost of Delay in Agile Projects with Time-Value Profiles

Summary:
The cost of delay for releasing a product can be due to many factors, but that value loss can seem like an abstract concept. Attaching hard numbers to a release timeline in the form of a time-value profile helps the development team and business stakeholders have a conversation about how long they have to build a product and when it would be best to enter a market.

The cost of delay for releasing a product can be due to many factors, but that value loss can seem like an abstract concept. Attaching hard numbers to a release timeline in the form of a time-value profile helps the development team and business stakeholders have a conversation about how long they have to build a product and when it would be best to enter a market.

About the author

[interview]

Shifting Left on Your Journey to Continuous Testing: An Interview with Adam Auerbach

Summary:

In this interview, Adam Auerbach, the senior director of technology for advanced testing and release services for Capital One Financial Corporation, shares his company's experience implementing continuous testing and describes its core principles.

In this interview, Adam Auerbach, the senior director of technology for advanced testing and release services for Capital One Financial Corporation, shares his company's experience implementing continuous testing and describes its core principles.

About the author

[article]

Instead of MVPs, Maybe We Should Be Releasing SMURFS

Summary:

The term minimum viable product, or MVP, has come to be misunderstood and misused in many organizations. It doesn’t mean you should be releasing half-baked, barely feasible software. Instead, you should be thinking of your product’s capabilities as a Specifically Marketable, Useful, Releasable Feature Set—or SMURFS!

The term minimum viable product, or MVP, has come to be misunderstood and misused in many organizations. It doesn’t mean you should be releasing half-baked, barely feasible software. Instead, you should be thinking of your product’s capabilities as a Specifically Marketable, Useful, Releasable Feature Set—or SMURFS!

About the author

[interview]

The Role of Artificial Intelligence in Testing: An Interview with Jason Arbon

Summary:

In this interview, Appdiff’s Jason Arbon explains what the rise of artificial intelligence means for the world of testing. He covers how manual testers can work with AI, the role of automation, and the type of companies that testers can now start.

In this interview, Appdiff’s Jason Arbon explains what the rise of artificial intelligence means for the world of testing. He covers how manual testers can work with AI, the role of automation, and the type of companies that testers can now start.

About the author

[article]

Weighing the Costs and Benefits of Mobile Test Automation

Summary:

Today’s market is teeming with attractive options for automating your mobile testing—each with a price tag. You may perceive mobile automation solutions as too expensive, but before you dismiss test automation as a viable solution for your business, let’s break down the benefits, options, and costs of automating your mobile QA process.

Today’s market is teeming with attractive options for automating your mobile testing—each with a price tag. You may perceive mobile automation solutions as too expensive, but before you dismiss test automation as a viable solution for your business, let’s break down the benefits, options, and costs of automating your mobile QA process.

About the author

[article]

4 Secrets to Successfully Scaling Agile Tech Teams

Summary:

There comes a time for every successful tech team to expand. But how do you scale in an agile way without losing productivity? Here are four secrets to successfully managing this transition, from deliberately choosing an incremental growth process to hiring new team members and retaining efficient communication.

There comes a time for every successful tech team to expand. But how do you scale in an agile way without losing productivity? Here are four secrets to successfully managing this transition, from deliberately choosing an incremental growth process to hiring new team members and retaining efficient communication.

About the author

[article]

How to Guarantee Failure in Your Agile DevOps Transformation

Summary:

Many organizations make the same agile and DevOps scaling mistakes year after year, then attempt to rectify them by putting together a great new strategy—only to miss the reasons causing the failure. If you want to refuse to evolve and, as a result, cause your organization’s agile and DevOps transformation efforts to deliver zero business value, be sure to follow these seven antipatterns.

Many organizations make the same agile and DevOps scaling mistakes year after year, then attempt to rectify them by putting together a great new strategy—only to miss the reasons causing the failure. If you want to refuse to evolve and, as a result, cause your organization’s agile and DevOps transformation efforts to deliver zero business value, be sure to follow these seven antipatterns.

About the author

Pages

CMCrossroads is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.