Being open-minded pays



Software can be built to behave exactly as specified. Or (much better), the customer can engage the technical experts in discussing innovative ways of approaching the business problem. For example, this could include opportunities to streamline the business, leveraging the latest technologies to improve performance, or building an architecture that is readily adaptable and supportive of the customer's ever-changing needs.

For example, a client recently asked Lab49 to build a batch-based system to replace a legacy system, for pricing a large portfolio of bonds. The large computational requirements for generating cashflows for the portfolio implied that only a couple of sets of prices could be generated throughout each day. The Lab49 team counter-proposed a system that modeled the portfolio of bonds on a more granular basis such that cash flows could be computed on demand in response to real-time inputs. This required less coding and could be delivered more quickly, allowed more flexibility and configurability, and provided a better solution to the customer's problem. This improved outcome was possible because the customer was willing to discuss the underlying business problems with Lab49 and engage in a dialog to identify the best solution.

Communicating at the right times

Issues, risks, dependencies and other impediments always surface during development, may of which require the stakeholders urgent attention. The last thing they want is for the development team to make important decisions around scope or the relative priority of features. So, when the team raises issues in real-time, the stakeholder must respond accordingly.

Specifying requirements is a tremendously difficult task. If the customer doesn't describe what he wants in enough detail, developers may build the wrong thing. But provide too much detail, and the developers may be pinned down and miss major opportunities to speed delivery. The best compromise is to discuss short-term requirements in a focused forum and stick to that plan for a complete development cycle (typically 2-3 weeks). Don't change the requirements in mid-cycle or the code will come out a mess! At the end of each development cycle the business stakeholders should review the work to date and provide guidance. At this point the requirements can be changed with minimal disruption.

-2-

Previous Page   

1  2  3  

   Next Page

Explore Our Topics

  • EDITOR'S BRIEFING
  • Virtual Conferences
  • Webinars
  • Roundtables

BPM in Action

March 10, 2011

The sixth annual BPM in Action 2011 Virtual Conference will explore cutting-edge market developments in BPM and describe how to leverage them for improved business operation and performance. More

View All Virtual Conferences

Smart Case Management: Why It's So Smart.

Date:Nov 05, 2009
Time:12:00 PM ET- (17:00 GMT)

REGISTER TODAY!

Date:Oct 29, 2009
Time:15:00 PM ET- (19:00 GMT)

REGISTER TODAY!
View All Roundtables
  • Research Library
  • Podcasts
  • News

Joe McKendrick: Part II of II: Designing Evolve-ability into SOA and IT Systems

In part two of Joe McKendrick's recent podcast with Miko Matsumura, chief strategist for Software AG, they talk about how SOA and IT systems need to change and grow and adapt with the organization around it.

Listen Now

Phil Wainewright: Helping Brands Engage with Social Media

Phil Wainewright interviews David Vap, VP of products at RightNow Technologies, and finds out how sharing best practices can help businesses understand how best to engage with online communities.

Listen Now

Peter Schooff: Making Every IT Dollar Result in a Desired Business Outcome: Scott Hebner of IBM Rati

Scott Hebner, Vice President of Marketing and Strategy for IBM Rational, discusses a topic on the top of every company's mind today: getting the most from IT investments.

Listen Now

Jessica Ann Mola: Where Will BI Fit In? Lyndsay Wise Explains

In BI, this tough economy and the increasing role of Web 2.0 and MDM are certainly topics on people's minds today. WiseAnalytics' Lyndsay Wise addresses each of them in this informative podcast.

Listen Now

Dennis Byron: Talking with...Deepak Singh of BPM Provider Adeptia

Deepak Singh, President and CTO of Adeptia, joins ebizQ's Dennis Byron in a podcast that gets its hand around the trend of industry-specific BPM.

Listen Now
More Podcasts
  • Most Popular
  • Quick Guide
  • Most Discussed

Quick Guide: What is BPM?

Learn More

Quick Guide: What is Event Processing?

Smart event processing can help your company run smarter and faster. This comprehensive guide helps you research the basics of complex event processing (CEP) and learn how to get started on the right foot with your CEP project using EDA, RFID, SOA, SCADA and other relevant technologies. Learn More

Quick Guide: What is Enterprise 2.0?

A lot of people are talking about Enterprise 2.0 as being the business application of Web 2.0 technology. However, there's still some debate on exactly what this technology entails, how it applies to today's business models, and which components bring true value. Some use the term Enterprise 2.0 exclusively to describe the use of social networking technologies in the enterprise, while others use it to describe a web economy platform, or the technological framework behind such a platform. Still others say that Enterprise 2.0 is all of these things. Learn More