BT
Older rss
  • Service Design: Consumer Journey Mapping

    by Deepak Arasu on  Feb 12, 2017

    A process of identifying key customer interactions with the product. This is a holistic approach to envisioning customer interactions at various touchpoints through service design tools to help organizations to understand, visualize and envision their new or existing customer there by aligning their products.

  • What Does "Being Digital" Actually Mean?

    by Reda Hmeid on  Jan 17, 2017 4

    Digital transformation is a key aim of many organisations these days, with varying levels of success. This is often due to a lack of understanding about what being digital really means, with emphasis on tech being obvious. This article gives a description of what Being Digital is and how it can be achieved.

  • Interview with Wesley Coelho on Challenges in DevOps

    by Shane Hastie on  Jan 04, 2017

    At the Agile 2016 Conference InfoQ spoke to Wesley Coelho, Senior Director of Business Development for Tasktop, about the communication challenges inherent in DevOps and how to overcome them; how DevOps and agile expose organisational silos and waterfall communications flows that need to become adaptive and automated.

Q&A with the Author on "Designing the Requirements”, an Alternative Approach

Posted by Rui Miguel Ferreira on  Nov 02, 2016

“Designing the Requirements: Building Applications that the User Wants and Needs" proposes an alternative way to deliver spot on solutions.

Standardizing Requirements Descriptions on Scrum Projects for Better Development and Testing Quality

Posted by Elena Belkovskaya on  Sep 24, 2016

Standardizing requirements descriptions on Scrum projects benefit development and testing quality by enablling full coverage, minimizing errors, and facilitating scheduling and requirements changes.

WTF requirements in Agile Product Development

Posted by Gene Gendel on  Aug 11, 2016

Iterative development requires gradual flow of small-sized, prioritized requirements from end customers to delivery teams. The use of all-conclusive, rigid, non-negotiable BRDs leads to dysfunction

Waterfall Requirements in Agile Product Development

Posted by Gene Gendel on  Aug 11, 2016

Iterative development requires gradual flow of small-sized, prioritized requirements from end customers to delivery teams. The use of all-conclusive, rigid, non-negotiable BRDs leads to dysfunction.

Why ALM Is Becoming Indispensable in Safety-Critical Product Development

Posted by Kristof Horvath on  Jul 15, 2016

The story of how Medtronic Neuromodulation realized that in order to modernize their processes while maintaining compliance, adopting integrated Application Lifecycle Management was necessary

User Stories Are Placeholders for Requirements

Posted by Russ Lewis on  Jun 06, 2016

It can be difficult to change from a Waterfall approach to the Agile practice in which requirements are prepared ‘just in time. The secret to success in Agile is ruthless management of scope.

Q&A with Dave Snowden on Leadership and Using Cynefin for Capturing Requirements

Posted by Ben Linders on  Apr 23, 2016

InfoQ interviewed Dave Snowden about applying leadership models, the Cynefin model and how it can be used for capturing requirements, scaling agile, and sustainable change.

Q&A with the Authors on "Requirements: The Masterclass LiveLessons-Traditional, Agile, Outsourcing"

Posted by Rui Miguel Ferreira on  Apr 17, 2016

InfoQ interviewed Suzanne and James Robertson on the "Requirements: The Masterclass LiveLessons - Traditional, Agile, Outsourcing" to get further insights into some of the topics addressed.

The Agility Challenge

Posted by Dragan Jojic on  Feb 04, 2016

In this article Dragan Jojic explores “the agility challenge”: A company where employees are able to sense and respond to external inputs without managers having to tell them what to do. 1

BT