DEC 23, 2013 11:00am ET

Related Links

Microsoft CEO Nadella Unveils Data-Analysis Tools for Companies
April 17, 2014
Gartner: CEOs Focus on Tech-Related Business Growth in 2014
April 17, 2014
Why You Need A Chief Information Security Officer
April 16, 2014

Web Seminars

April 29: Create a data protection strategy with open, software-defined storage
April 29, 2014
New Best Practices To Manage Customer Information
May 7, 2014
May 13: Cost-effective, scale-out backup in 1 solution
May 13, 2014

When Agile BI is Not Agile


Through our collective experience at my firm, my colleagues and I have collaborated on many different projects together. And in just about every case, our differing backgrounds required us to adapt or assimilate different methodologies put forth by members of the team or our clients.

Get access to this article and thousands more...

All Information Management articles are archived after 7 days. REGISTER NOW for unlimited access to all recently archived articles, as well as thousands of searchable stories. Registered Members also gain access to:

  • Full access to including all searchable archived content
  • Exclusive E-Newsletters delivering the latest headlines to your inbox
  • Access to White Papers, Web Seminars, and Blog Discussions
  • Discounts to upcoming conferences & events
  • Uninterrupted access to all sponsored content, and MORE!

Already Registered?

Filed under:


Comments (4)
Ahhh . . . "Agile" development, the programmers' methodology for focusing on the tree leaf -- never mind the entire tree -- & making it damn near impossible for those responsible for the forest (read: ENTERPRISE information architecture) to plan, document, or account for the resources available & spent. "Agile" development . . . the excuse programmers use for justifying repeated failed attempts at delivering products users want or need in lieu of taking the time up-front to acquire actual data & system requirements. "Agile" development . . . the sneering attitude programmers visit upon technical database administrators when admonished to use platform functionality instead of their own cloudy crystal balls to foresee or prevent the majority of stupid user tricks -- stupid user tricks which those self-same technal DBAs now must repair. "Agile" development . . . back to the bad old days of programmers writing 100 lines of code so twisted & convoluted (with NO documentation or explanation, often with the sole purpose of retrieving something as mundane as the date & time from a server) so that s/he created a permanent revenue stream for her/himself -- no one else can read the code, much less decipher it. Ahh . . . "Agile" development . . .
Posted by Jolene J | Thursday, December 26 2013 at 8:51AM ET
I have been working on an MDM project following agile (what client calls) methodology. One of the key issue we constantly face is the challenges in getting the work done by other teams which do not follow agile. Often this results in undelivered code & failure to meet the commitment done to business owner.

Can you please throw some light on how you handle this? I am somewhat convinced this problem is in most of the organizations as not many follow agile methodology enterprise wide. Getting work from colleagues outside core agile team is a major pain area.

Posted by Prashanta C | Saturday, December 28 2013 at 7:57PM ET
Add Your Comments:
You must be registered to post a comment.
Not Registered?
You must be registered to post a comment. Click here to register.
Already registered? Log in here
Please note you must now log in with your email address and password.

Are you actively evaluating master data management technologies and their ability to scale and support emerging trends around big data, social and mobile?

Yes 61%
No 23%
Don't Know 9%
Not Applicable 6%


Login  |  My Account  |  White Papers  |  Web Seminars  |  Events |  Newsletters |  eBooks
Please note you must now log in with your email address and password.