DevOps brings Development and Operations together with the sheer objective of ensuring quality and enabling faster time to market. However, what happens to QA in this scenario? How does the Testing team fit in? Let's ponder on this further and understand the role of QA and Testing in the DevOps world ...
The DEVOPSdigest Vendor Forum was established to give vendors of DevOps-related technologies an opportunity to share their views with the IT community in an objective venue. All commentary in Vendor Forum blogs is intended to be objective, vendor-neutral and non-promotional content to educate and enlighten our readers.
All vendors in DevOps-related market spaces are welcome to blog on the Vendor Forum at no cost. To request a blogging account on the Vendor Forum, contact Pete Goldin, Editor and Publisher of DEVOPSdigest.
Signing Up for a Vendor Forum Blogging Account
■ A request for a blogging account on the Vendor Forum must come directly from the individual whose name will be on the blogs, from that individual's corporate email address.
■ Only one representative from each vendor will be allowed to maintain a blogging account for the Vendor Forum at any particular time, if that vendor does not sponsor DEVOPSdigest. Once a company's blogger is established, that same byline must be used for all future blogs from that company. The only time the byline can be changed is if the blogger is no longer with the company; the blogger has moved to a different part of the company and no longer has any involvement with DevOps; or the blogger is no longer blogging and has not posted a blog for a long time. To change the blogger for your company, contact Pete Goldin, Editor and Publisher of DEVOPSdigest.
■ DEVOPSdigest sponsors are allowed multiple blogging accounts on the Vendor Forum. Platinum and Gold Sponsors are eligible for an unlimited number of blogging accounts, and Silver Sponsors are eligible for up to 8 blogging accounts. This sponsor benefit is especially helpful for companies with multiple thought leaders in the industry who would like to claim authorship for their own blogs. Click here to find out how you can sponsor DEVOPSdigest.
■ If a blogger leaves a company, moves to a new company, and continues to blog, all blogs posted by that blogger – past and present – will reference the new company. References to the previous company will be removed from the previous blogs. This would only happen if the blogger remains in the DevOps industry or a related market.
Rules for Blogging on the Vendor Forum
Please observe the following rules when blogging on the Vendor Forum:
■ Do not promote your own company, products or partners in blogs on the Vendor Forum. Topics should be general industry interest. Copy and graphics should be non-promotional and vendor-neutral.
■ One reference to your company in the blog copy is permitted when you are discussing a survey or report conducted or commissioned by your company. A reference to your company's or partner's product is never permitted in the blog copy.
■ If your blog is about a study or survey conducted or commissioned by your company, focus on the results of the survey/study, not why and how the survey/study was conducted.
■ A reference to open source projects is sometimes permitted, as long as the reference is to the open source project or technology itself, and not the company that founded or owns the project. DEVOPSdigest will make a determination on a case by case basis.
■ Do not criticize a company, brand or product in any blogs on the Vendor Forum.
■ Companies that do not sponsor DEVOPSdigest can only include a link to their company home page at the end of the blog – no product pages or any other pages. Even if the product has its own URL separate from the company page, this cannot be included in place of the company home page. The home page link will always be included in the "Related Links" section at the end of the blog, and cannot be substituted with a hyperlink in a marketing message.
■ Only sponsors of DEVOPSdigest can include additional links at the end of the blog, to other pages on their websites, white papers, webinars, articles, blogs, product pages, etc. Click here to find out how you can sponsor DEVOPSdigest.
■ DEVOPSdigest removes old outdated links, but only updates outdated links for current sponsors of the site.
■ Do not place any hyperlinks in the body copy of a blog linking to your company's or any other vendor's web pages or other promotional pages. Hyperlinks in the body copy should only be to support factual points you are making. Hyperlinks in the body copy should only be to support factual points you are making. These hyperlinks can link to a supporting report or article as long as the content is not on your website or your partner's website, is not sponsored or commissioned by your company or partner, and does not promote your company or your partner company in any way. Inclusion of any hyperlinks is at the sole discretion of DEVOPSdigest.
■ Try to keep blogs between 500-1000 words. This is more of a guideline than a rule. You can include more content if you wish, but DEVOPSdigest recommends posting shorter blogs more often. If you have written a 1000+ word blog, consider breaking it into two or more blogs, and post them a couple weeks apart. You could call them Part One and Part Two, if you want.
■ All blogs will be reviewed by DEVOPSdigest prior to publication. DEVOPSdigest reserves the right to edit any content submitted, and the publication of any blog is at the sole discretion of DEVOPSdigest. Vendor Forum blog posts are edited by DEVOPSdigest for spelling, basic grammar and punctuation. Vendor Forum blogs are also edited to ensure they meet DEVOPSdigest guidelines.
■ A Vendor Forum blogger can either log into the DEVOPSdigest system to post their own blogs, or send copy to the editor, who will post the blog under the blogger's name. Once the blogger saves a blog in the system, it does not automatically publish. The system notifies the editor, who will review and publish.
■ The date the blog is actually published will be decided by the editor. DEVOPSdigest may provide you with an estimated date the blog will be posted, but that date cannot be guaranteed, as unforeseen priorities may push the posting date back.
■ DEVOPSdigest sponsors have priority posting. This means that sponsor blogs go to the front of the queue, usually posting within a day or two. The only factors that could delay posting of a sponsor blog would be other sponsor blogs already in the queue, or content that must be posted due to timeliness.
■ Do not save an unfinished blog in the system. The Vendor Forum blogging system does not enable bloggers to go back into a blog and edit it later. Once a blog is saved in the system, it is considered ready to be published, assuming it meets DEVOPSdigest guidelines. So only save blogs in the system when they are ready to be published.
■ If a blogger posts their own blog, and wants to include a graphic with the blog, the graphic must be added by the editor.
■ All Vendor Forum blogs must be original content that has not been published somewhere else. DEVOPSdigest periodically may request to re-post a blog, if the content is particularly valuable to our readers, but please do not re-post your blog on DEVOPSdigest, or pitch DEVOPSdigest to re-post your blog.
■ You can re-post your blogs from the Vendor Forum on your own blogs or websites, as long as you mention that the blog was posted on DEVOPSdigest, and include a link to our site. However, we recommend linking to the blog on DEVOPSdigest.com rather than posting the full blog on your site, to highlight the fact that the content was published by an independent third party. Publication of your blog on a respected industry site provides strong thought leadership credibility for the author and company.
■ Please note that these guidelines are updated periodically to ensure continued alignment with DEVOPSdigest's mission.
Topics for the Vendor Forum
DEVOPSdigest accepts Vendor Forum blogs on topics relating to DevOps, including:
■ Development Processes
■ Development Technology
■ Development Automation
■ Agile Development
■ Continuous Development
■ API (Application Program Interface)
■ Development Monitoring and Analytics
■ Application Performance and Quality Testing
If you are unsure whether your topic fits DEVOPSdigest, run your idea by Pete Goldin.
When organizations adopt containers and microservice style architectures in production, systems become incredibly complex. For operations it's a shock because it means coming to grips with many new container tech nuances - plus letting go of the old monitoring rule book ...
Managing application performance today requires analytics. IT Operations Analytics (ITOA) is often used to augment or built into Application Performance Management solutions to process the massive amounts of metrics coming out of today's IT environment. But today ITOA stands at a crossroads as revolutionary technologies and capabilities are emerging to push it into new realms. So where is ITOA going next? With this question in mind, DEVOPSdigest partner site APMdigest asked experts across the industry for their opinions on the next steps for ITOA ...
In Part 3 of my Q&A with industry analysts, I ask: What trends will have the biggest impact on the software industry and DevOps in particular this year and beyond? How can enterprises set themselves up to succeed with so many rapid changes occurring in development and delivery? ...
In Part 2, I'll dive into some findings from CollabNet's outreach to industry analysts. I asked them about the greatest challenges facing enterprises venturing into the world of DevOps and to touch on what lies ahead for the future of the DevOps movement ...
DevOps teams bring significant benefits to their organizations. Unfortunately, DevOps teams, like many business programs, tend to believe innovation must come with a detriment to security. Security measures are often seen as obstacles that impact the agility that DevOps teams rely on ...
With increased competition, enterprises now require greater agility than ever before, and traditional approaches simply can’t provide the speed enterprises demand. To remain competitive with these new players, companies need to improve their operational agility both in the data center and the WAN ...
There is no "right" culture for DevOps, but characteristics such as open communication, high cooperation, collaboration, respect, and trust are essential. If your organization does not have these characteristics, they must be developed. Culture is learned, not inherited. It must be genuinely nurtured by everyone from executive management on down the line. Here are some hacks to help develop a positive DevOps culture ...