Call for Papers
Below is the call for papers for the upcoming Cutter IT Journal issue Does Agile = Better DW/BI? guest edited by Lynn Winterboer.
- Abstract Submission Date: 31 October 2013
- Articles Due: 12 December 2013
- Guidelines for Contributors
Does Agile = Better DW/BI?
The amount of data available to organizations to analyze and use in decision-making is exploding. "Big Data" is all the rage and organizations of every size from every industry are struggling to make valuable use of the information available from their operational systems, business partners, and social networks. Organizations, seeking to respond quickly in an ever-changing marketplace, are hungry for current and useful information about their eco systems. Data Warehousing and Business Intelligence teams are working as fast and hard as they can to meet this ever-increasing demand with limited resources and time. Fortunately, DW/BI teams who embrace an "agile" approach are finding they can meet the top priority needs in short timeframes and with higher quality than they could using a traditional "waterfall" approach to project management.
However, like many disciplines in life, agile concepts are relatively simple to explain yet often difficult to master. For example, what are the risks and rewards of asking DW/BI specialists to become Agile DW/BI generalists? What concerns do we have about designing a DW solution in an iterative fashion, and how can we ensure the benefits outweigh the risks? What is the "vision" of a successful Agile DW/BI team, to which teams in transition can aspire?
An upcoming issue of Cutter IT Journal addresses Agile Data Warehousing/Business Intelligence and invites practical advice, insight and actual case studies on how an Agile approach increases the value DW/BI teams deliver to their organizations. We also seek insight on the possible challenges and risks faced by DW/BI teams working in an agile framework, and specific practices that can ensure your DW/BI team's agile transformation goes smoothly.
Topics may include, but are not limited to, the following:
- What are the benefits and pitfalls of using an agile approach to DW/BI?
- Why do DW/BI teams find agile transformation difficult and how can they overcome those concerns?
- How will the roles/dynamics of the BI department and its stakeholders be affected by an agile transformation?
- Do agile DW/BI teams basically "look and feel" the same around the globe, or do cultural differences impact how data teams embrace agile frameworks?
- What cultural/organizational challenges must be overcome for a successful DW/BI agile transformation?
- What lessons have you learned, and/or best practices would you share, based on your own DW/BI agile transformation?
- What new business models or technological capabilities can be enabled with an agile approach to DW/BI?
- What does agile look like for Big Data, compared to traditional DW/BI?
- How do DW/BI departments effectively scale their agile practices as their departments grow?
- Which agile approach is best suited for a DW/BI Team -- Scrum, Kanban, XP, or others?
- What are the key considerations for a DW/BI team in determining which approach to use?
- In which business scenarios have you found an agile approach to DW/BI to have the most impact?
- How can stakeholders benefit from supporting their DW/BI team in an agile approach?
- What infrastructure issues must be considered for a DW/BI team to successfully deliver in iterations? What are the hardware and software implications of an agile approach to DW/BI?
- How can Agile DW/BI lead to higher ROI, better decision making, and market responsiveness?
- What can a DW/BI team learn from other IT teams who have already gone through an agile transformation?
- What is the role of external consultants and coaches in an agile transformation?
- Which non-functional requirements (the "ilities") are most impacted by an agile approach to DW/BI?
- How can an agile DW/BI team mitigate risks and embrace opportunities that occur with an agile approach?
- What are the intangible benefits of transitioning to an agile approach to DW/BI?
- What are the challenges faced by a DW/BI product owner and how can the organization mitigate these risks?
- What is unique about testing data? Which automated testing practices and tools work best for agile DW/BI teams?
- Is there a minimum set of agile skills a DW/BI team should have, and is there a certification path or a standard?
- Will an agile approach only work for large established DW/BI teams? Is there a size limit on which teams can effectively take an agile approach?
TO SUBMIT AN ARTICLE IDEA
Please respond to Lynn Winterboer at lwinterboer[at]cutter[dot]com, with a copy to cgenerali[at]cutter[dot]com no later than 31 October 2013 and include an extended abstract and a short article outline showing major discussion points.
Accepted articles are due by 12 December 2013.
Most Cutter IT Journal articles are approximately 2,500-3,500 words long, plus whatever graphics are appropriate. If you have any other questions, please do not hesitate to contact CITJ's Group Publisher, Christine Generali at cgenerali[at]cutter[dot]com. See the editorial guidelines.
Important Note: When you submit an article to Cutter Consortium, you warrant that you (or your employer) are the sole owner of the article and that you have full power and authority to copyright it and publish it. Also, the article you submit to Cutter must be an original; not previously published elsewhere.
Typical readers of Cutter IT Journal range from CIOs and vice presidents of software organizations to IT managers, directors, project leaders, and very senior technical staff. Most work in fairly large organizations: Fortune 500 IT shops, large computer vendors (IBM, HP, etc.), and government agencies. 48% of our readership is outside of the US (15% from Canada, 14% Europe, 5% Australia/NZ, 14% elsewhere). Please avoid introductory-level, tutorial coverage of a topic. Assume you're writing for someone who has been in the industry for 10 to 20 years, is very busy, and very impatient. Assume he or she will be asking, "What's the point? What do I do with this information?" Apply the "So what?" test to everything you write.
We are pleased to offer Journal authors a year's complimentary subscription and five copies of the issue in which they are published. In addition, we occasionally pull excerpts, along with the author's bio, to include in our weekly Cutter Edge e-mail bulletin, which reaches another 8,000 readers. We'd also be pleased to quote you, or passages from your article, in Cutter press releases. If you plan to be speaking at industry conferences, we can arrange to make copies of your article or the entire issue available for attendees of those speaking engagements -- furthering your own promotional efforts.
ABOUT CUTTER IT JOURNAL
No other journal brings together so many cutting-edge thinkers, and lets them speak so bluntly and frankly. We strive to maintain the Journal's reputation as the "Harvard Business Review of IT." Our goal is to present well-grounded opinion (based on real, accountable experiences), research, and animated debate about each topic the Journal explores.