Guest Editor: Eric Willeke
Abstract Deadline: January 25, 2021
Article Deadline: February 26, 2021
Digital transformation has many definitions, all of which revolve around doing things to satisfy your customers and operate your business more effectively, predictably, quickly, cheaply, and consistently through applying technology. As these basics fall into place, digital increasingly becomes about how quickly you can adapt to changing customer desires and continue to improve their experience across all channels. Achieving these goals requires change across many dimensions of your business, especially in how people come together to create and evolve the technology your business relies on.
Meanwhile, Agile and DevOps provide well-established guidance on the most effective way to create and evolve technology, and each is rapidly expanding the range of problems it attempts to address as companies and communities take on ever-larger challenges using the techniques.
It’s time to bring those threads together and focus on how today’s incarnations of Agile and DevOps can most directly support digital transformation. Business and technology leaders need help as they align purposes, simplify conversations, ease turf wars, smooth siloes, serve their customers, and find pain relief by addressing the gritty realities of the complexity faced by large enterprises seeking transformational change. Articles don’t shy away from naming the reality, describing the underlying root cause, and providing tactical, actionable advice on how to begin creating change.
An upcoming issue of Cutter Business Technology Journal, with Guest Editor Eric Willeke, will provide focused insights on how leaders can use the goals, principles and mindsets of Agility and/or DevOps to accelerate the journey to digital transformation, inspire change, overcome resistance, and produce real results in the most complex organizations.
Articles ideas may include, but are not limited, to the following:
- What are the most critical aspects of Agile and/or DevOps for a digital transformation executive?
- What lessons have we learned from Agile and/or DevOps transformations that a digital transformation should consider?
- What pitfalls do digital transformations face when applying Agile and/or DevOps practices?
- What Agile and/or DevOps practices should a digital transformation focus on applying first?
- What should Agile and/or DevOps transformations learn from a digital transformation, and how can digital transformation executives ensure those lessons aren’t forgotten in their own transformations?
- What goes wrong in a digital transformation if Agile and/or DevOps aren’t adopted?
- What new behaviors are expected from leaders in digital transformation when Agile and/or DevOps are being used effectively?
- How can Agile and/or DevOps inform how a digital transformation itself is managed?
FOR CONSIDERATION: Please send an abstract (~ 400 words or less of proposed article content and author(s) bio) to Eric Willeke and Christine Generali. Final article length is typically 2,000-3,500 words plus graphics. More editorial guidelines.
Guest Editor: Michael Papadopoulos
Abstract Deadline: January 25, 2021
Article Deadline: February 26, 2021
For businesses undergoing a digital transformation, a Low Code/No Code (LC/NC) approach to development can be a catalyst to innovation, boost productivity, and even address a developer shortage. How? LC/NC solutions provide declarative development options with relatively low learning curves that provide a company’s workforce with the tools needed to easily create software to grow and transform the business.
The benefits of LC/NC platforms are demonstrated in their ability to empower entrepreneurial people in the organization, or citizen developers, to unleash their visions, ideas, and creativity with minimal support through building smart software solutions. This approach can save a business time and money while accelerating the pace of digital innovation and transformation within their organization.
An upcoming issue of Cutter Business Technology Journal with Guest Editor Michael Papadopoulos seeks insight on the advantages, limitations, use cases, business opportunities, and applications of a low code/no code development platform.
Articles ideas may include, but are not limited, to the following:
- How do LC/NC application development platforms compare to traditional development platforms? When/why is one preferred over the other?
- What are the advantages/limitations of a LC/NC platform?
- Why is LC/NC going to be so important in the future?
- What important priorities ensure LC/NC success?
- How can you determine if LC/NC tools can best serve your strategic objectives?
- What type of architecture and organizational structure can help facilitate the introduction of LC/NC solutions?
- What level of operational process and quality standards should you demand from your first LC/NC applications?
- What are some examples of successful LC/NC applications/use cases?
- How we can make LC/NC a part of our standard software applications lifecycle?
- How can we run LC/NC applications as part of a Continuous Integration/Continuous Delivery environment?
- Can LC/NC platforms and tools help bring about the democratization of AI?
FOR CONSIDERATION: Please send an abstract (~ 400 words or less of proposed article content and author(s) bio) to Michael Papadopoulos and Christine Generali. Final article length is typically 2,000-3,500 words plus graphics. More editorial guidelines.
Guest Editor: Ron Zahavi
Abstract Deadline: December 21, 2020
Article Deadline: January 28, 2021
IoT solutions are evolving beyond asset tracking to complex interactions across environments. Such solutions include management of facilities and spaces, tracking the product manufacturing lifecycle, and tracking products through the supply chain. But maintaining and making changes to equipment and building products to understand behavior once operational can be costly. It’s more effective to capture insights, predict outcomes and respond to real changes in the world, and to model and simulate the impact of the change or to explore how a product will behave before it is built. Digital twins are virtual representations of physical things (people, places, assets, etc.) or processes and can be used to understand, build, operate, and manage real things. Digital Twins can model any environment and create a synchronized model of that environment, track its past, simulate possibilities, and predict its future. Digital Twins can be used to drive better products, optimize operations and costs, and improve customer experiences.
Digital twins have been used for decades by organizations such as NASA, but technologies such as the cloud, IoT, and AI have made building a wide range of digital twin solutions more practical. Digital twins can be used to model industries and environments that include machines, factories, buildings, stadiums, oil rigs, and even entire cities and country infrastructures, and to represent the human body to address healthcare and COVID.
As the digital twin market has been emerging, there is some confusion about what a digital twin means and how to apply it. What makes something a digital twin and how do you identify it? What are the different types of digital twins? What processes and product lifecycle stages are appropriate for digital twins? What investment is required and what is the value and expected return on investment? What are the risks and security concerns of digital twins since they may control real assets or cross ecosystems managed by different parties? What digital twin standards are available or missing?
An upcoming issue of Cutter Business Technology Journal will address these questions and present strategies for meeting the challenges of newly emerging digital twin technologies, solutions, and opportunities.
Articles ideas may include, but are not limited, to the following:
- What are examples of digital twin solutions and their architectures?
- What are the different types of digital twins?
- How should CEOs and CIOs evaluate the readiness of their organizations to tackle digital twins?
- What business opportunities can be leveraged utilizing digital twins?
- What new concerns, risks and threats are posed using digital twins and how can they be addressed?
- What industries and use cases can benefit from digital twins?
- How are standards and ecosystems being addressed in the market?
- What are some simulation methods and models of digital twins?
- What are the components of a digital twin and how do they interoperate within a digital twin, with legacy systems, and with other digital twins?
- Describe a case study and the resulting ROI derived from the use of digital twins
FOR CONSIDERATION: Please send an abstract (~ 300 words or less of proposed article scope and author(s) bio) to Ron Zahavi and Christine Generali. Final article length is typically 2,000-3,500 words plus graphics. More editorial guidelines.
These notes are intended to give authors some guidance and direction for articles submitted to Cutter Business Technology Journal (CBTJ) for publication.
Length: The average article in CBTJ is 2,000-3,500 words, unless otherwise specified by the Group Publisher.
Article Format: Please send your article in word document format for editing purposes. Please do not send it as a PDF.
Editorial: Cutter Business Technology Journal is professionally edited by our team who evaluates articles for content, substance, grammar, and style and provides valuable feedback so that authors can revise and improve their papers before publication. Publishing turnaround times are short. Articles are also peer-reviewed by the Guest Editor who is an expert in the field.
Audience: Publishing with Cutter affords the opportunity to present your insights and research to a global corporate audience that is highly interested in emerging developments. Typical readers of CBTJ range from CIOs, CTOs, business technology executives and vice presidents to directors, technology managers, project leaders, and very senior technical staff. Most work in fairly large organizations: Fortune 500 organizations, universities, large computer vendors, NGOs/IGOs, and government agencies and spanning industries such as finance and banking, education, energy, entertainment, food, government, healthcare, insurance, and manufacturing. 48% of our readership is outside of the US (15% from Canada, 14% Europe, 5% Australia/NZ, 14% elsewhere).
Editorial advice: Introductory-level, tutorial coverage of a topic is not very popular with our readership because they're fairly senior people. Delete the introductory "fluff" and get to the meat of the 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 is mentally asking, while reading your article, "What's the point? What do I do with this information?" Apply the "So what?" test to everything you write.
General comments: We enjoy controversy and strong opinion; we like the fact that we can provide an alternative to standard "refereed" journals that sanitize articles. Because we don't carry any advertising, we can publish critical or negative comments about specific vendors or products. However, we obviously don't want to publish anything libelous or slanderous. Conversely, we don't publish self-serving commercial messages praising one's own product or service.
Style, grammar, and mechanics: For advice on good writing style, we recommend Merriam-Webster's Collegiate Dictionary, 11th ed., The Chicago Manual of Style, and The Elements of Style (Strunk and White). We are fanatics about the editorial quality of Cutter Business Technology Journal; anything you can do to help us in this regard will be greatly appreciated.
Graphics: Please keep your use of graphics to a minimum and submit original, editable files (not static images). Preferred formats include MS Excel for graphs, MS Word for tables (1-2 pages), and MS PowerPoint/MS Word/Adobe Illustrator (v17 or less) for vector art. Please send all other types as high-res JPEG, PDF, PNG, or TIFF. All images owned by another party may only be used with owner’s permission. It is the author’s responsibility to obtain permission. Copying images off the Internet without permission infringes on copyright and is unacceptable for publication.
All graphics (figures and tables) must include captions and a reference within the text; for example, “(see Figure 1)” or “Figure 1 illustrates….” Please note that we may remove graphics deemed unnecessary. Please be minimalistic in your design: limit colors, shadings, and typefaces. For additional questions, please contact Linda Dias (email@example.com).
Deadlines: The deadline you agree to when you commit to writing an article is a "hard" deadline; if you're going to be late, let us know and we'll negotiate a mutually agreeable delivery date. If the deadline passes without our having heard from you, we will assume that you have vanished and are unable to provide the article.
Editorial process: Once we get your article, we commence two parallel editorial passes: one for content (by the guest editor) and one for substance, grammar, and style (by our managing editor, Cindy Swain (firstname.lastname@example.org). Either or both of these editorial reviews may result in some questions or feedback from us. In any case, we will send you a first draft "page proof" of your article for your review and approval. Articles published in the journal must meet certain criteria relating to audience, technical content, and presentation. In the unlikely occurrence that, upon editorial review, your completed article does not meet with these requirements, Cutter Consortium reserves the right to decline the publishing of your article in the journal.
Biographical sketch: At the end of each CBTJ article, we like to include a brief (200 words or less) biographical sketch of each author along with email address of author(s). Click here for a sample. We also like to provide a color headshot. Please include a high-res color headshot (at least 300x300 pixels in size) of each author. We accept formal or casual photos that present authors in a professional manner. For samples, see the “Meet the Cutter Experts” section at https://www.cutter.com/our-experts.
Copyrights: When you submit an article to us, you warrant that you (or your employer) are the sole owner of the article, that you have full power and authority to copyright it and publish it, and that it has not been previously published elsewhere. You also warrant that it does not infringe on any copyright, violate any property rights, or contain scandalous, libelous, or unlawful matter.
Sourcing Content: When you do draw on the work of other authors and researchers, cite your sources accordingly in the relevant part of the text (using endnote numbers or hyperlinks). Given that Cutter Consortium has no relationships with vendors, we cannot permit the use of references, quotes, statistics, and figures from analyst/research firms with vendor ties (Gartner, MetaGroup, Yankee Group, Forrester, IDC, McKinsey, among others), as the data may be biased. If you feel information from one of these sources is critical to your article, please bring it to our attention early in the editorial process and we will be happy to discuss the issue. Note that Cutter Consortium conducts studies and surveys occasionally in its various practice areas. This data is available for use in your articles or reports. If there is specific data you are looking for to support an argument, please contact us for more information. We will be happy to send you any relevant data.
Keep in mind that if your article uses too many sources, it is often an indicator that your piece summarizes research too heavily and lacks original thought. Remember our readers are interested in your insights; above all, speak in an expert voice.
Promotion: We will, at your request, provide you with a link to share with your colleagues and contacts where they can register and receive a complimentary PDF download of your complete article. You can post this link on your website, blog, tweet it, promote on social networks, etc. It is only acceptable for your final, Cutter-edited article to be downloaded from the Cutter site, and it may not be posted anywhere else without express permission from Cutter*. You may also excerpt a passage or section from your article with attribution to CBTJ, and link it back to the full article on the Cutter website. We also ask that once the issue is published, that you do not post the entire issue PDF on any websites or social media sites out of respect for our paid clients/subscribers.
* CBTJ accepts no advertising, has no outside sponsorship, and is completely subscriber-supported. In order for us to continue providing this venue for debate to our authors, and your valuable insights to our subscribers, we thank you in advance for your respect of our copyright.
Author Compensation: We are pleased to offer Journal authors an online, one year complimentary subscription to Cutter Business Technology Journal upon the signing of the license agreement. In addition, we occasionally pull excerpts, along with the author's bio, to include in our weekly Cutter Edge email newsletter, which reaches another 12,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 the issue in which you're published available for attendees of those speaking engagements -- furthering your own promotional efforts.
Reprints: If you would like an authorized reprint of your article for promotional purposes or to post on your website, contact Customer Service (Tel: +1 781 648 8700; E-mail: email@example.com) for more information. We can arrange for a reprint with the CBTJ cover, logo, and other details.
Endnotes/References: When you draw on the work of other authors and researchers, please cite your sources. All sources/side commentary must be noted in relevant part of text (using endnote numbers) and listed in sequential order (i.e., order of appearance, not alphabetical order) at end of article in “Endnotes.” All sources should include basic publishing information (i.e., author(s) name(s), complete title, publisher, date, and hyperlink and/or URL). Sources can be repeated but must be listed as a new endnote. The following are examples of various types of endnotes:
1DeMarco, Tom, and Timothy Lister. Waltzing with Bears: Managing Risk on Software Projects. Dorset House, 2003.
2In this survey, “innovation” refers to any new initiatives to introduce innovative, leading-edge, or unconventional software project development methods, processes, tools, or techniques.
3Hall, Curt. “AI & Machine Learning in the Enterprise, Part XI: Success of AI Application Development Efforts.” Cutter Consortium Data Analytics & Digital Technologies, Executive Update, Vol. 19, No. 3, 2019.
4DeMarco and Lister (see 1).
5“Smart grid.” Wikipedia.
||Emerging Trends in AI
||Low Code/No Code: Empowering the Citizen Developer & Unleashing Innovation
||Agile/DevOps: Facilitating the Journey to Digital Transformation
||Data & Digital Architecture
||Fintech: COVID-19 Impact and Opportunities for Economic Growth
||Philip O'Reilly and Kevin O'Leary
||Cultivating Diversity & Inclusion in the Workplace
||mHealth: The New Frontier in Healthcare
||Proactive Risk Management
||Crisis Alert! Strategies for Today and Beyond
||Beyond Automation: AI, ML, RPA
||Trust: Is IT the Problem or the Solution?
||Want Happy Customers? Make Your Employees Happy!
||Business Technology Trends and Predictions: 2020
||Data Architecture is Really About People
||Martijn ten Nepal
||Blockchain: New Industry Trends, Developments, Use Cases
||Blockchain: Here to Stay?
||Digital Architecture: The Spark for Transformation
||Gar Mac Críosta
||Caution! AI Consequences Ahead
||Is Software Eating the World?
||Cutting Edge Agile II
||Technology-Empowered Solutions: Redefining Decision Support
||Dr. Karen Neville and Dr. Andrew Pope
||Cutting Edge Agile
||The Next Frontier in Automation: Opportunities, Challenges and Impact
||Business Technology Trends & Predictions 2019
||Fintech: Emerging Trends, Future Directions
||Riding the Next Wave of Cloud Computing
||Frank Khan Sullivan
||Building a Digital Business Starts with Data
||The Critical Need for Governance
||Architecture + Agile: The Yin & Yang of Organizational Agility
||Fog/Edge Computing: Opportunities, Case Studies, Challenges
||Transforming the Customer Experience
||Blockchain: Where Are We Now? Where Are We Headed?
||A Disciplined Agile Approach to Business Agility
||Scott Ambler and Mark Lines
||AI: Fear It, Face It, or Embrace It
||Business Technology Trends and Predictions 2018
||Change Leadership in a Digital Era
||Trends in Big Data Technologies and Analytics
||Insurtech: Reinventing the Insurance Industry
||Agile Leadership: Foundation for Organizational Agility
||The Industrial Internet: Driving Digital Transformation
||Leveraging Enterprise Architecture for Digital Disruption
||Beyond Fintech: New Frontiers
||The Frontier of Fintech Innovation
||Business Opportunities in the New Digital Age
||Information Superiority and Digital Capital
||Borys Stokalski and Bogumil Kaminski
||The 21st Century Technology Leader
||Technology Trends, Predictions, and Reflections 2017
||FinTech and the Digitization of Financial Services
||Cognitive Computing: Applications, Trends, and Implications
||Business-Driven Digital Transformation
||Security in the Internet of Everything Era
||Patrikakis Charlalampos and George Loukas
||Cultivating Success in Big Data Analytics
||The Role of Ethics in Algorithm Design
||IoT Data Management and Analytics
||Bhuvan Unhelkar and San Murugesan
||Technical Debt: The Continued Burden On Software Innovation
||Disruption and Emergence: What do they mean for Enterprise Architecture?
||Technology Trends and Predictions: 2016