IDEAS home Printed from https://ideas.repec.org/h/spr/fuobcp/978-3-031-36429-7_8.html

Agile Principle 1: “Our Highest Priority Is to Satisfy the Customer Through Early and Continuous Delivery of Valuable Software”

In: Leading Modern Technology Teams in Complex Times

Author

Listed:
  • Kevin R. Lowell

Abstract

Delivering valuable software frequently is the name of the game. Developers and customers have different definitions of what constitutes value. You learn what “value” means to your customer by bringing her together with your team. You accomplish this through dialogue. The dialogue generates clarity of requirements and a common understanding of the process. Developing software that satisfies the quality, speed, and value expectations of customers is what matters most. This is what customers want and need, and this is what they are paying you for, so this is what you as the leader must deliver. Leaders of agile software development teams know that this is far easier said than done. It involves dialogue, iterative development, risks, and failures. Vignettes from leaders at Nokia, UScellular, and Centene Corporation illustrate these leadership challenges and how to address them. It begins with dialogue. You as the leader bring your agile software development team together with the business owner to establish and execute a sustainable, repeatable process for prioritizing requirements, defining what will satisfy the customer and how the customer will use the software solution, and defining what the customer deems valuable. The objective of joining the teams and executing the process is to generate solutions. Leaders overcome challenges by implementing a repeatable and sustainable process for generating solutions. Teams must agree on what “valuable” means and what “continuous” means. Answers aren’t revealed. Rather, solutions are generated, and they’re generated through dialogue.

Suggested Citation

Handle: RePEc:spr:fuobcp:978-3-031-36429-7_8
DOI: 10.1007/978-3-031-36429-7_8
as

Download full text from publisher

To our knowledge, this item is not available for download. To find whether it is available, there are three options:
1. Check below whether another version of this item is available online.
2. Check on the provider's web page whether it is in fact available.
3. Perform a
for a similarly titled item that would be available.

More about this item

Statistics

Access and download statistics

Corrections

All material on this site has been provided by the respective publishers and authors. You can help correct errors and omissions. When requesting a correction, please mention this item's handle: RePEc:spr:fuobcp:978-3-031-36429-7_8. See general information about how to correct material in RePEc.

If you have authored this item and are not yet registered with RePEc, we encourage you to do it here. This allows to link your profile to this item. It also allows you to accept potential citations to this item that we are uncertain about.

We have no bibliographic references for this item. You can help adding them by using this form .

If you know of missing items citing this one, you can help us creating those links by adding the relevant references in the same way as above, for each refering item. If you are a registered author of this item, you may also want to check the "citations" tab in your RePEc Author Service profile, as there may be some citations waiting for confirmation.

For technical questions regarding this item, or to correct its authors, title, abstract, bibliographic or download information, contact: Sonal Shukla or Springer Nature Abstracting and Indexing (email available below). General contact details of provider: http://www.springer.com .

Please note that corrections may take a couple of weeks to filter through the various RePEc services.

IDEAS is a RePEc service. RePEc uses bibliographic data supplied by the respective publishers.