Tag: training

  • The Linux Foundation Adds Free Jenkins Training Course

    The Linux Foundation Adds Free Jenkins Training Course

    The Linux Foundation, in collaboration with the Continuous Delivery Foundation (CDF), today launched a free introductory course to the open source Jenkins continuous integration/continuous delivery (CI/CD) platform as part of what it plans will become a series of free and paid online DevOps tools courses.

    Clyde Seepersad, general manager of training at the Linux Foundation, said that while the foundation already provides access to some higher-level conceptual DevOps courses, the launch of the CDF last year provides a knowledge base from which the Linux Foundation can now provide online courses specific to DevOps tools. The CDF is an arm of The Linux Foundation.

    The Linux Foundation will also provide courses on Spinnaker, a CD platform, and other DevOps tools that, along with Jenkins, are now being developed under the auspices of the CDF, he added.

    In general, Seepersad said demand for DevOps expertise is increasing as organizations more aggressively embrace digital business transformation initiatives in the wake of the COVID-19 pandemic. At the same time, IT teams are adopting a wider range of cloud-native technologies to build more flexible and resilient applications. DevOps platforms such as Jenkins make it possible for IT teams to build those applications faster.

    The challenge many organizations underestimate is the extent of changes to their internal IT culture required to make that transition, Seepersad said—too many organizations still put tools into the hands of developers without really thinking through the workflow issues between developers and IT operations teams.

    The most important thing for any organization to do, he said, is to make sure there is an open DevOps dialogue versus tiptoeing around issues that will tend to increase resistance only further.

    Ultimately, free training should help expand the overall size of the DevOps community at a time when many IT professionals are trying to increase their skills. DevOps professionals not only command higher salaries, but they are also less likely to be laid off. DevOps teams oversee the development and deployment of applications and can also programmatically manage levels of infrastructure that IT administrators relying on traditional graphical user interface (GUI) tools can’t match. That’s a critical issue when many IT organizations these days are trying to do a lot more with even less.

    There’s nothing quite like an economic crisis to focus everyone’s mind. The biggest DevOps challenge any organization typically faces is overcoming inertia. Too many IT professionals have relatively narrow skillsets that conspire to increase the total size of the IT organization. In addition to relying on increased levels of automation to reduce costs, IT leaders want to be able to scale IT environments without having to increase headcount.

    It may take a little while longer for the transition to DevOps to fully play out. However, it’s now more of a question of existential survival rather than if or even to what degree to embrace DevOps. Organizations that don’t embrace DevOps processes to ruthlessly automate the management of IT now might very well never get another chance.

  • The Best Approach to Help Developers Build Security into the Pipeline

    The Best Approach to Help Developers Build Security into the Pipeline

    Speed and agility are at the core of digital transformation and DevOps culture, and have quickly become a business imperative for organizations that want to remain competitive. Speed cannot come at the sacrifice of security, though. The pace of software development requires that security be baked into the code from the start rather than tacked on after the fact. Developing secure code fast requires empowering developers with the skills and tools they need and building security into the DevOps pipeline.

    Embracing DevSecOps

    DevOps culture and the drive to work faster and more efficiently affects everyone in the organization. When it comes to creating software and applications, though, the responsibility for cranking out code and producing quality code falls on developers.

    The pace of DevOps culture doesn’t allow for anything to be an afterthought. It’s important for developers to support security directly as a function of application development in the first place, and to operationalize security within the continuous integration/continuous deployment (CI/CD) pipeline.

    Unfortunately, traditional education does little to prepare them. It’s possible to get a PhD in computer science and never learn the things you need to know to develop secure code. As organizations embrace DevSecOps and integrate security in the development pipeline, it’s important to ensure developers have the skills necessary. You also need to focus on both the “why” and the “how” in order to build a successful DevSecOps training program.

    Don’t Just Check the Box

    Not all training is created equal. Consider why you’re doing the training and the outcome you hope to achieve rather than doing training for the sake of training. Many organizations focus on training developers in secure coding practices from the perspective of compliance. It’s crucial to engage developers in a meaningful way, though, and not just check a box.

    Many compliance frameworks, such as PCI-DSS, require ongoing application security training, but compliance training often reinforces the wrong lessons. Developers learn the most expedient way to check the box and achieve compliance rather than learning the most efficient way to develop secure code. This approach also causes developers to feel like the security team looks down on them or doesn’t understand the challenges they face or the expectations they have to meet.

    The Carrot and the Stick

    How you do security is also important. Training works better when developers feel like they are part of the process and when they have a reason to want to excel.

    For nearly everyone, doing something in practice reinforces lessons better than just reading content or listening to a webinar or video. Interactive labs are more engaging and provide feedback as developers go through the training. They can practice writing secure code with guided practice that is self-paced. They can also get hands-on experience exploiting vulnerable applications, then patching them back up.

    You should implement developer training that creates incentives for developers by gamifying training. Create custom Capture the Flag events, track individual progress and provide a leaderboard that enables healthy competition among the developers.

    You also want to provide developer training that is relevant to your organization’s preferred coding languages and business objectives. The training should teach skills and strategies that are applicable to the code your developers work with and give them tools they can use immediately to improve the security of the applications they’re working on.

    Speed is essential for businesses to maintain a competitive edge today, and security is more important than ever. Make sure you have the training in place to help shift application security knowledge left and integrate security to mature DevSecOps practices.

  • The Linux Foundation to Award 500 Training Scholarships

    The Linux Foundation to Award 500 Training Scholarships

    The Linux Foundation this week announced it will make up to 500 training scholarships available this year.

    Clyde Seepersad, general manager for training at the Linux Foundation, said the number of Linux Foundation Training (LiFT) Scholarships being made available is being increased because of both the demand for individuals with particular expertise such as Kubernetes and the fact that more people are spending more time at home. As such, many IT professionals have more time available to advance their skills, said Seepersad.

    Unfortunately, there are going to be many more unemployed IT professionals as the COVID-19 pandemic wreaks havoc across the global economy. Many of those individuals will need to attain additional certifications to compete in an IT job market that suddenly has much less demand and a pool of job candidates that has increased seemingly overnight.

    The scholarships being made available by The Linux Foundation are designed to encourage individuals with varying types of backgrounds to develop open source software expertise. They include:

    Open Source Newbies
    Teens-in-Training
    Women in Open Source
    Software Developer Do-Gooder
    SysAdmin Super Star
    Blockchain Blockbuster
    Cloud Captain
    Linux Kernel Guru
    Networking Notable
    Web Development Wiz

    Since 2011, more than 100 training and certification scholarships valued at more than $220,000 have been awarded by The Linux Foundation. The deadline for applying for the latest round of scholarships is April 30.

    The Linux Foundation is also making available its entire catalog of paid eLearning and certification exams available at 30% off through April 7.

    Seepersad said all the courses made available by The Linux Foundation are accessible online. Each exam administered is also recorded. Interestingly enough, Seepersad said the number of potential cheating incidents is far less online than in classrooms mainly because each individual taking an exam is recorded. There’s also more opportunity to potentially share answers in a traditional classroom setting, he noted.

    It’s unclear precisely how the COVID-19 pandemic might impact demand for IT skills going forward. While it’s clear there will be fewer IT professionals employed, there may be an actual increase in demand for individuals with open source expertise. During the last economic downturn many organizations adopted an “open source-first” philosophy to acquiring software as part of an effort to reduce IT costs. Many of those organizations determined they would rather allocate their much-reduced IT budgets to retaining IT staff than paying for commercial software, even if that meant the time and effort required to implement and manage that software was higher.

    At the same time, it’s worth noting many organizations may need to accelerate the rate at which they are modernizing their IT environments. Now that most employees and end customers are spending most of their time at home, many organizations are finding their existing portfolio of applications do not lend themselves easily to being remotely accessed. Some might even take advantage of open source container technologies to lift and shift entire existing legacy applications into the cloud because their IT staff may not be able to physically access a local data center for more than a month.

    Whatever the ultimate outcome, the one thing that is for certain is working in enterprise IT environments will never be the same again.

    — Mike Vizard

  • Upping IT Skills: IT Pros Cite Significant Challenges

    Upping IT Skills: IT Pros Cite Significant Challenges

    Anyone who works within enterprise technology learns very quickly that if they want to stay relevant to the workforce, they’ll need to continuously learn new skills. But it’s certainly hard keeping up with new skill training while also keeping pace with day-to-day work demands.

    This is probably why a survey earlier this year from IT management software provider SolarWinds found that 70% of all technology professionals surveyed do not feel completely confident that they have all the necessary skills they’ll need to successfully manage their IT environments over the next three to five years.

    A certain amount of fear that one’s current skillsets may become antiqued by technological change is worthwhile, but that apprehension is only useful if technology professionals turn that energy into action. According to a more recent SolarWinds survey, 60% of technology professionals haven’t actively pursued learning a new skill or completed a certification in the last six months.

    The survey, Building Confidence for Tech Pros of Tomorrow, is based on an international survey of 177 technology professionals within both the public and private sectors. It was fielded in August 2019.

    The survey found roughly 50% of the technology professionals who did start a certification process did not finish. The primary reason was lack of time.

    Enterprises, aware that there exist challenges when it comes to finding the staff with the skills they need, are making efforts to mitigate their staffing challenges. These efforts predominately involve internal trainings, with 35% of respondents citing such training. Additionally, 54% of respondents said full-day in-person workshops provide the most value for the time spent.

    The survey also found soft skills are becoming increasingly important, with 46% of respondents stating interpersonal communications skills are the most critical for career growth. Other top skills were project management (56%) and public speaking/presentations (52%).

    Interesting, the majority of technology professionals surveyed said, while they are confident speaking with business leaders, they don’t believe they are adequately equipped with the support and tools they need to be effective at their work. According to the survey, the top two requirements for technology professionals to become confident managing current and future environments include increased budget/additional resources (64%) and more support from IT or business leadership (48%).

    Finally, and which could be a sign of the increased reliance of enterprises on software, the survey found application performance management (APM) skills are increasingly necessary for technology professionals. Survey respondents cited application support, troubleshooting and monitoring as tasks they are increasingly responsible. And 53% said user experience monitoring of applications is an additional skill of theirs that they are required to develop.

    — George V. Hulme

  • DevOps and Collaboration: Fraternizing with the Enemy?

    DevOps and Collaboration: Fraternizing with the Enemy?

    DevOps is all about collaboration, we hear.
    “You must collaborate,” say managers initiating DevOps adoption programs.
    HR make new posters declaring the corporate values “We value Collaboration & Teamwork.”
    Can’t fail!
    Then when it appears not to be as effective as we had hoped we tell teams they are “Empowered” to collaborate.
    Blank stares!
    When things still don’t appear to be working we tell teams they are “self-steering,” “self-organizing, collaborative teams”….
    Still, we don’t get what we were hoping for.
    Luckily the tool vendors come to the rescue and tell us why it is failing. We need “collaboration tools and software” – Throw some “Slack” at it.
    Can’t fail!

    This is when we usually get frustrated managers knocking on our door asking about the Phoenix Project DevOps simulation. They are moaning about communication and collaboration! When we talk to the teams they are frustrated and moaning about “empowerment” and managers not “walking the talk.”

    In my mind these lack of collaboration skills is not really surprising. Why?

    Impression: Well, it doesn’t help when the word has also historically been connected to global conflict situations. “He faces charges of collaboration,” “fraternizing with the enemy.” Dev & Ops. Traditional adversaries?

    Interpretation: The interpretation of the word itself is also part of the problem. I googled an English Language Help Desk:

    Collaboration: “To work together with somebody in order to achieve a single shared goal.”
    Cooperation: “Work with other people by achieving one”s own goals as part of a common goal.”

    In an HBR article titled, “There’s a difference between cooperation and collaboration,” it was argued  “… Managers mistake cooperativeness for being collaborative,” adding, “… most managers are cooperative, friendly, willing to share information – but lack the ability and flexibility to align their goals and resources with others in real time.” If managers don’t get it then what chance do the teams have when told – “You must collaborate”!

    Induction: Part of our failure to be able to effectively collaborate could come from our schooling. We are chastised at school for asking others for help, for looking to see how somebody else is doing it—”That is cheating”—things are changing with more “collaborative assignments.” Yet, my children (now in their early 20s) were not taught what effective collaboration is, other than discovering for themselves. As my daughter explained about her school assignment, “You have to do it yourself if you want it done because others will slink off and not do it, then my individual grade may suffer.” They are told they need to collaborate but individual performance grades are scored. My daughter once came home stressed and almost in tears, declaring “Oh no! I have been given another collaborative assignment for my most important subject!” Children leave schools distrustful of collaborating.

    Indoctrination and Imperative: There is also the historical perspective. When we, the current workforce entered our chosen profession we had decades of functional silos that created a “them” and “us” attitude. This stimulates a sort of “territorial imperative” or “tribalism,” not helped by our own “technology” languages and tribal cultures. We have learned over time that other teams “dump things on us” or other teams “stop us from getting stuff done.” In other words, Other teams frustrate work.  (Territorial imperative—”the drive in animals and man to take, hold and defend a particular area, zone, turf,” —e.g. defending their best practice framework! And attacking others that come near!).

    Inconsistency: We then built walls between these teams and if they wanted something from each other they needed to escalate it to their manager. Managers would collaborate or not, especially when they were given conflicting, inconsistent goals and KPIs. Development teams are given goals to release as fast and as often as possible. Operations are given goals to make sure everything is as reliable as possible and available at all times.

    I had an example of this “them and us attitude,” once with a board of directors. I split them into two teams and gave each team a pack of ABC cards (Attitude, Behavior and Culture) and within 10 seconds heard, “Oh good, our team will win this!” automatically creating an atmosphere of competition and winning and losing, I hadn’t even explained the task yet! Teams compete.

    ‘It’ factor: A study by Google (2012) called Project Aristotle, named in tribute to Aristotle’s quote, “The whole is greater than the sum of its parts,” looked into why some teams work and others don’t. One of the key conclusions was that “psychological safety” was the “it” factor, “… a sense of confidence that the team will not embarrass, reject or punish someone for speaking up.” Because we have not learned to collaborate and because we have a “them and us” history often accompanied by blame, there is fear, uncertainty and doubt (FUD) about speaking up, sharing ideas or giving feedback.

    In the dark: However, there is another significant reason for poor collaboration, as I have discovered from running hundreds of Phoenix Project simulations with teams globally. It is the fact that nobody has defined the “behaviors” that demonstrate effective collaboration. We assume everybody knows what we mean when we say, “You must collaborate.” Fact: We don’t!

    Below are the results of a series of recent Phoenix Project simulations. One of the goals was to learn DevOps practices such as CALMS and the Three Ways, while another goal was to learn effective team-working and collaboration.

    I asked the teams at the start of the sessions, “What is effective collaboration? What behaviors will I see today that demonstrate this”?  The teams came up with a list of behaviors (each team came up with a top five or six behaviors; this is the consolidated list from seven teams).

    • Transparent communication – “open and honest” and “frequent.”
    • Calm and constructive dialogue (no blame, accusations and shouting).
    • Feedback “asking for and giving feedback.” Constructive feedback.
    • Shared team goals (and cross team). What are we aiming for? Impact on others and their goals. Maybe conflicts that need managing.
    • Listen – is it clear and understood? Show that you listen.
    • Being open for dialogue, being approachable –not closing the door or hiding behind.
    • Giving and taking responsibility.
    • Sticking to agreements.
    • Central moment to get together (e-2-e).
    • Knowing the roles and responsibilities, sticking to responsibilities.
    • Mistakes are OK.
    • Be proactive to get information needed.
    • Equal treatment: “Respect” ideas from ALL
    • Don’t HOPE, confirm.
    • “Willingness.” Confirm and agree.
    • Ownership of responsibilities.
    • Clear agenda and purpose of meetings.
    • Pleasure – celebrating success.

    “Are these behaviors you want to see more of in your daily work?” I asked.

    Yes! Was the answer.

    “Do we now all commit to sticking to these behaviors today, in this simulation?

    Yes! Was the answer. Easy! See there’s nothing to this collaboration stuff.

    However …

    During the simulation it soon became evident that roles and responsibilities were not clear or not being carried out; it was not agreed which information was needed by the business nor when; goals were unclear, meaning that priorities were arbitrary; people did not understand procedures and did not ask for help; assumptions were made (“I told you …,” “I thought you meant …”); people taking responsibility were not respected (“Let’s stop and try and sort this out …”)— everybody just carried on running around! “Headless chickens,” said one delegate; people were not listening to each other; there was a lot of “assumicide”; mistakes were made and people blamed—there was no exploration as to why and what can be done to stop these  mistakes. Mistakes were often corrected by somebody else but without giving any feedback to correct future mistakes; agreements were unclear across the team; there was no end-to-end flow—work and information was ping-ponging back and forward.

    “All in all, just like reality!” declared the teams.

    See how easy collaboration is. Within one hour of making a list of desirable behaviors, they were totally, utterly and universally ignored. Nobody appeared to own these behaviors or to confront each other on them.

    After the Experiences in Simulation

    At the end of the simulation round we looked at the team scores (number of releases, number of successful releases, business value realized). It wasn’t a pretty sight. The CEO wasn’t happy. The team felt stressed, unhappy, frustrated and powerless.

    We explored what this had to do with “effective collaboration.” Had anybody used the list of behaviors? No.
    Had anybody consciously practiced these behaviors?
    No.
    Did anybody give feedback on these behaviors when they were clearly not done?
    No.
    “Giving feedback feels strange, it feels like we are criticizing and blaming,” said one delegate. Another assumption!

    “It’s hard,” said one delegate. “The manager needs to manage this,” said another.
    “It was YOUR list and YOU all agreed this, why is this a manager’s job to get you to do what you said you wanted to do?”
    There was silence. “It’s not easy, we fall back into old ways of doing things, we need help!”

    Is it a Bird, Is it a Plane, Is it a Bus? No, it’s a coach!

    As the simulation progressed, the team refined their list of desirable behaviors based upon their experiences. They were coached for two rounds and consciously practiced and experimented with the behaviors. The coach role became a critical catalyst.

    In the final round the team owned, and were executing on these behaviors without coaching.
    Why were they suddenly executing?
    They felt less stressed; they were trusting each other; they felt the positive impact on their work; they saw, felt and shared the value gained by these behaviors. They felt immediate positive consequences from these behaviors.
    Why no more coaching?
    The team were taking it in turns to lead their own stand-ups; they were giving feedback and correcting their own behaviors. These were the additions the teams made to the behaviors as they practiced them.

    • Transparent communication – “open and honest” and “frequent” (Relevant, and timely as agreed with the various stakeholders).
    • Feedback “asking for and giving feedback.” Constructive feedback. (Related to agreed behaviors and responsibilities, calling stop, then swarming to solve an impediment, constraint, or remove waste; immediate fact based feedback).
    • Shared team goals (and cross team). What are we aiming for? Impact on others and their goals. Maybe conflicts that need managing. Understanding strategic portfolio and how we contribute to strategy, show you understand and agree common goals and prioritize accordingly. Goals for both value creation (features and benefits) and value leakage (risks, debt).
    • Leadership within team – team members took turns in facilitating the stand-up and retrospective. This role was respected.
    • Listen – is it clear and understood? Show that you listen, sender: Ask for clarification, ask to confirm understanding, listener: summarize what was understood and agreed. Avoid assumptions.
    • Being open for dialogue, being approachable—not closing the door or hiding behind. All were engaged and equal in the stand-up and retrospective. All were asked for feedback, ideas, suggestions.
    • Giving and taking responsibility. Respecting team behaviors; e.g if somebody calls “stop,” or “respect somebody taking responsibility for an improvement stand-up.”
    • Sticking to agreements. Confront people to understand why agreement not met and what can be done about it in the future (e.g conflicting priorities, lack of understanding).
    • Central moment to get together (e-2-e). Scheduled stand-ups, retrospectives, and improvement prioritization.
    • Knowing the roles and responsibilities, sticking to responsibilities, confirming your responsibilities, confronting people on responsibilities (feedback). Showing that you take ownership.
    • Mistakes are OK – no blame, so long as it is used as an opportunity to learn and improve.
    • Be proactive to get information needed (or ensure information is available, e.g. visible management board, avoid unnecessary “disruptions).
    • Equal treatment: “Respect” ideas from ALL. Ask people for input, engage ALL in ideas generation and decision-making.
    • Don’t HOPE, confirm.
    • “Willingness.” Confirm and agree – “Willingness” and “ability,” empower to be able. Share knowledge, cross train, coach, help.
    • Ownership of responsibilities. Confronting people on responsibilities.
    • Clear agenda and purpose of meetings. My role, what is expected from me? What is in it for me? avoid “wasting” time in meetings.
    • Team coaching to give feedback on behaviors.
    • Create trust by demonstrating team behaviors.
    • Check understanding and commitment to “agreements” and confront people (feedback) on agreements.
    • Improving own work as a team.
    • Asking for and offering help.
    • Having insight, overview, visibility.
    • Limit WIP (reserve WIP for learning, improving, technical debt).
    • Pleasure – celebrating success. Product owner shared results including customer feedback. Team complemented each other.

    The teams were then asked to make a list of behaviors and actions they wanted to take away and apply. Their line managers and assigned team coaches were there when the list was made and gave commitment to help guide, coach and empower teams to experiment and practice these new behaviors in their daily work.

    The team would prioritize one or two behaviors to start with and consistently practice in the coming weeks. When the new behavior becomes the accepted norm and a “habit” they would focus on more behaviors.  This fits in with the Third Way of DevOps: Continuous experimentation and learning. “Understanding that repetition and practice is the prerequisite to mastery.” And to tie this back to Aristotle the philosopher (not the Google project): “Excellence is an art won by training and habituation … We are what we repeatedly do. Excellence, then, is not an act but a habit.”

    Meetings, Including Training Sessions!

    And finally, one of our industry’s most popular, and wasteful, examples of collaboration are poorly run meetings, which are the biggest time-sink in organizations and a source of frustration. I include some training classes as forms of meetings.

    In more than 100 training sessions in the last year, less than 10 percent have started on time.
    Nine minutes late is the average. Delegates say this is normal in their organizations. When I ask people what their own personal learning goals are for sitting eight hours in this “training meeting,” more than 25 percent had not defined this and more than 70 percent had not agreed this with the “sponsor” of the training.

    We need to manage our overload of wasted meeting effort. How? One way is the ask for goal and agenda in advance, asking what value you need to bring in and what value you need to get from the meeting; also to limit your time to the agenda items relevant for you or your team.

    Efficient collaborators decide when they do, or don’t, have unique value to add—“maintaining focus on what matters.”

    The same applies to training, asking, “Why am I going on the training?” “What am I expected to learn?” “What problem is this training expected to help solve?”  “What will I be expected to do differently after the training?” “How will the learning be transferred back to the workplace?” “Will I be mentored and coached?” “Will I be given opportunities to experiment?” “Will I get constructive feedback?” “How can we demonstrate that the new knowledge delivers expected benefits?” This is better than the most common answer, “I don’t know I was told to come to this training!”

    A training is also a form of collaboration between you, the trainer and the person sponsoring the training.

    There is an “I” in Team, after all. “I” am responsible for my effective contribution to team performance.

    — Paul Wilkinson

  • Industry benchmarking tools to fill skills gap

    Cloud Academy, an enterprise-ready training platform that accelerates teams and digital transformation, is announcing industry benchmarking tools designed to help organizations define the critical job roles and technical skills needed for cloud adoption and ongoing competitiveness.

    One example of Cloud Academy’s data includes a comparison of AWS, Microsfot Azure and Google Cloud. The data indicates knowledge of AWS is far above the other two (image below). Other examples include required skills (image below), trending skills and job role demand by geo, trending technology and real-time, data-driven definition of cloud job roles.

    Any interest in speaking to Cloud Academy? Or, would you like to speak to customers (such as Turner or Pokemon’s head of security), receive data and visuals, or review the embargoed release?

    Screen Shot 2018-10-12 at 2.36.45 PM.png

    Screen Shot 2018-10-12 at 1.34.30 PM.png

     

    Comparison between R and Python: While R is getting significant hype, the data shows that Python is actually the language most organizations require prospects know.

  • A Certifiable Reason to Attend Training at DevOps World | Jenkins World 2018

    A Certifiable Reason to Attend Training at DevOps World | Jenkins World 2018

    There are many factors that make DevOps World | Jenkins World the essential DevOps event to attend each year. Whether it is the keynotes and speaker sessions from industry-leading DevOps experts, the expo where you can check out the latest and greatest from our friends in the software industry or the themed after-party, there are many reasons why year over year the conference grows. An added benefit that contributes to DevOps World | Jenkins World being the DevOps event of the year is the wealth of informative preconference training and certification. Think of them as the workout before the big game, providing you the tools and knowledge to make the most of the conference and beyond.

    The growth of attendance and variety of attendees of  the DevOps World | Jenkins World conference is one of the indicators that the industry is constantly innovating and evolving. Last year, Forrester declared 2018 as the “Year of DevOps,” with 50 percent of survey respondents reporting they had already implemented DevOps with plans to expand. For DevOps practitioners to keep up with the continuous pace of modern software development, there also has to be continuous learning. Training and certification at DevOps World | Jenkins World will cover relevant topics in software development, such as authorization and security, build management, instance administration and interfacing with cloud services, in addition to Jenkins and CloudBees Core fundamentals.

    Not only are all training sessions available to add on to your full conference sessions pass, but you also can receive a free Jenkins certification exam voucher—a $150 value—for the Certified Jenkins Engineer (CJE) and Certified CloudBees Jenkins Platform Engineer (CCJPE) exams. You can choose to sign up for an onsite exam at DevOps World | Jenkins World (first-come, first-serve) or use it at a later date. There are also several half-, one- and two-day courses that can be added during the event registration process.

    In addition to our recommendations below, check out the Training and Certification page to see what courses can help strengthen your software delivery pipeline skills.

    DevOps Leader Certification Training

    Successful implementation of DevOps requires leadership. Whether you are in a  tactical or strategic role, if you help design, influence, implement or motivate the cultural transformation in DevOps adoption, this course will take your DevOps leadership to the next level.

    Value Stream Mapping for DevOps

    If you’re looking to better understand DevOps, you are in the right place! Join Mike Orzen, a recognized and prominent Lean thought leader and author, to learn the ins and outs of DevOps value stream mapping, helping you identify inefficiencies in your current process, and optimize it to deliver more value to your customers.

    Jenkins Fundamentals

    It wouldn’t be Jenkins World without Jenkins! To prepare yourself for both the Certified Jenkins Engineer (CJE) or Certified CloudBees Jenkins Platform Engineer (CCJPE) certifications, Jenkins Fundamentals introduces you to the best practices for leveraging Jenkins to drive your continuous development life cycle with Jenkins.

    CloudBees Core Fundamentals

    As the foundation of CloudBees, once you’ve mastered Jenkins Fundamentals, CloudBees Core Fundamentals is the obvious next step. In this training, attendees will gain the skills needed to leverage the CloudBees Core product suite to successfully scale CD and DevOps in their organizations. The training includes an overview of the key proprietary features provided with CloudBees Core to enhance the capabilities of Jenkins.

    CloudBees Core on Kubernetes

    Kubernetes is seeing widespread adoption as the operating system for cloud native applications and the industry’s go-to container orchestration system. This course will provide attendees with the tools needs to run CloudBees Core on Kubernetes, and leverage public and private clouds to establish an elastic, scalable CD and DevOps platform. The course includes hands-on installation of CloudBees Core on Kubernetes. 

    Go to https://www.cloudbees.com/devops-world to learn more and to register. Additionally, use this special code just for devopsy.kinsta.cloud readers—JWDEVOPSCUST—at registration, and you’ll get a 20 percent discount.

    — Brian Dawson

  • DevOpsGroup Academy Launch: Interview with Head James Harvey

    DevOpsGroup Academy Launch: Interview with Head James Harvey

    DevOpsGroup Academy launched in July with a mission to eradicate the UK’s tech skill shortage and invest in the high-performing IT professionals of the future. I recently had a chance to speak with DevOpsGroup Academy Head James Harvey about the mission and vision for DevOpsGroup Academy and what he sees for the future of technology learning.

    Hartley: Can you tell us more about the launch of DevOpsGroup Academy in July 2018, your university connections and addressing the skills gap?

    Harvey: I think the biggest challenge that we’ve seen is that, even though you are getting hundreds of thousands of students graduating with computer science degrees over the years, the gap that we are experiencing between what people are learning at university versus what the commercial world is demanding is astronomical.

    We’ve seen, with our intern program, for example, if you compare an intern who has spent a year with us directly with someone who is freshly graduated—the difference in terms of ‘work readiness’ beyond comprehension. It’s insane!

    The skills gap is one of those things that is very difficult for universities to keep on top of, because things in the tech world change rapidly and dramatically. So ultimately what you are learning is often outdated by the time you finish anyway. It’s a different skill set that you learn at university: It’s very lecture-based, it’s very academic and it’s very blue-sky. And it’s very much “in an ideal world” setting.

    Whereas what we are trying to do with The DevOpsGroup Academy is to say, when things aren’t quite so perfect and when you do have to be a bit more pragmatic and apply some of the things you have learned on a bigger scale, then we can help bridge that gap.

    The first instance of the launch of The DevOpsGroup Academy is really going to be focused on the fact that these are commercial courses that we are selling to people who are looking for a career change, looking to enhance the skills of their team or whatever it might be. And the fact that we run these courses with students, interns, graduates, associates, apprentices and placements even will become a huge selling point for us. But the initial target for us is going to be those small businesses, SMEs, and individuals looking to skill up.

    Hartley: Can you talk about The DevOpsGroup Academy and what you’re offering that’s unique?

    Harvey: There are, of course, plenty of DevOps courses that you can find out there from many other suppliers. The big USP (unique selling proposition) for us when it comes to public training is that we are not this “one-stop shop” for agile DevOps or tech training. What we pride ourselves in is having a carefully selected portfolio of courses that align with our company values, and aligns with the way in which we go in and facilitate a transformation. And critically, these courses and our portfolio have been chosen so that they form this kind of learning journey, this development pathway, so that if you take one course there is something else that is related that makes sense to go and do elsewhere.

    I mean, it would be very easy for us to sit down and say, “Right, we are going to run these 50-odd training courses that we can offer.” But then, as I said, the difference there is that we would just become another training company, which we are not trying to do.

    The other USP that we have got is that we don’t typically use trainers to deliver the training. We use our practitioners and the people who are doing this day in and day out to deliver the training, because again we feel that it allows them to give you a more realistic demonstration of what it is we are trying to teach you. Rather than somebody who has been training for 10 years and has lost touch with what the pragmatic, real-world looks like.

    So it allows us to take all of the experience that we have got in DevOpsGroup and regurgitate that, as not just textbook training, but as this real-life experience that we’ve been through. So learn from our mistakes and learn from our successes. That’s the wisdom that we can impart.

    Hartley: So are there any specific new courses that you are launching with DevOpsGroup Academy?

    Harvey: The main focus at the moment will be around the Agile Foundation certification, and we are in the process of getting toward the end of launching a certified DevOps Foundation training course.

    There are a few other DevOps training courses out there, but it’s definitely not a crowded marketplace and it’s something that we’ve developed internally, because we didn’t feel that there was a suitable option out there for that kind of agnostic learning, to get a DevOps Foundation certificate for.

    Hartley: Going back to universities and government, can you talk more about those partnerships?

    James Harvey: You can look at our partners’ page on the new DevOpsGroup Academy website for a bit more information on our current university partnerships.

    We are very much focused on working with all of the local universities in Wales at the moment, so we do a lot of work with the National Software Academy that’s based at Cardiff University. They do things a little bit differently in that their computer science students are working in what is a much more commercial environment, where they do a lot more hands-on with workplace technologies and things like that.

    DevOpsGroup Academy has introduced a summer placement scheme with the National Software Academy, to help their students take the learnings that they’ve got from university to a different level. Part of what made that happen is that, because we’ve had that relationship with them up until now, the level that the students are at means that they can come in for a few months and actually do some work that adds some value, both for us and for them.

    Beyond that, we are doing things like giving guest lectures at universities across Wales and just trying to get involved as much as we can. The end game for us, really, is to help facilitate and extend the learning that the students get in the classroom. So how can we ultimately become a finishing school for students wanting a career in IT? And it’s about doing that while working as closely as possible with our university partners and without completely condescending the university system.

    Hartley: Going back to addressing the skills gap. What can you say about the limitations of university computer science courses?

    Harvey: It’s a different type of learning. Universities are crippled somewhat by the overarching governance around getting syllabuses together. And what we have found is that a lot of the time there is a resistance to change those.

    So, for example, if you were ever going to have a commercially relevant computer science degree, for example, you would be looking at revising that syllabus every year at the very least, considering how technologies moves on and what becomes relevant and not relevant.

    And I think it’s very difficult then, because there is this emphasis at the university level on broad learning and not specializing in a specific thing. So it’s difficult then for students to pick up things and to get in and get their hands dirty and add value to what it is they are doing. So there is a lot of general learning that goes on, and the general feedback that we get is that they just don’t have that space to get their hands dirty. To try things out. To fail, if need be.

    And that’s the difference between the university and us. The whole point of our intern program, for example, is that the whole point of their learning over the year is continued. And their learning is accelerated.

    So I do think that it’s probably fair to say that they learn more from the 12 months they spend with us, than they do from their first two years at university. But that’s because we are able to accelerate that academic learning by ultimately letting them get hands on with the tech. And that’s one of the most difficult things for universities to be able to do at scale: to allow students to get into the nitty-gritty, if you like, because it’s very difficult to govern that and test that and so forth.

    Hartley: In terms of teaching agile and DevOps processes at university, how does that work?

    Harvey: Really badly! Those that are doing it, generally, will take agile or DevOps and they will treat it as a module. And that is taught for a semester.

    Instead, what you should be seeing is that agile and DevOps should be this underpinning thing that runs throughout your entire three years at university. So everything that you do, you are constantly learning about how to implement that in an agile way.

    I’ve been doing guest lecturing at universities in Wales for the past five years and that has been my underlying theme—that there are some things that shouldn’t be taught as modules. They should be underpinning everything that you are doing. And that’s one of the big things we learn from our interns—on the first few weeks they are here we will give them an Agile Foundation training course and then that underpins everything that they do from that point onward whilst they are here.

    So time and time again, with regards to specific agile and DevOps practices and ways of working, we are seeing that it is being shoved in as a module and, ironically, more often that not towards the end of a degree course. Rather than at the beginning, when students could benefit from learning about it off the bat.

    But then again, a lot of university work is done in isolation and it’s working on small solo projects, which doesn’t lend itself well to a lot of agile and DevOps practices and processes. The types of projects that they are working on at university simply don’t mirror what you find in a commercial world. Universities work in isolation; they are not working with businesses and local people; the curriculum is all in isolated modules that are not interlinked in anyway. The barriers need to be brought down if we are going to work in a collaborative way.

    Hartley: Is breaking down those barriers the long-term mission of the DevOpsGroup Academy?

    Harvey: Yeah, definitely! I think the long-term goal for us is all about that accelerated learning. Learning as you are working and as you are going along. And allowing and giving people the space to do that, to learn from each other, to collaborate.

    We are ultimately disrupting and changing the norm of what goes on right now, because the one thing about university learning is that it doesn’t set you up for starting your career once you’ve graduated. You are learning about these small, isolated examples that don’t really set you up for work in the commercial world.

    So if you give these students the space and environment to do this accelerated learning, then within six months they are very close to what you would consider to be an associate-level engineer that comes into our organization. Which is extremely powerful for us. And it sends a really strong message about the educational methods that we use and the partners that we work with as far as training is concerned.

    Ultimately we are doing this, as we’ve always said, because we want to invest in the next generation of talent. We are expanding rapidly and we are doing this because we want to give these kids jobs, in the end.

    Hartley: What about the start-up scene in Wales and Welsh government funding for DevOps training for SMEs?

    Harvey: Yeah, one of the pilot schemes that we are working on at the moment are “boot camps”—the idea being that an SME would send one or two people along to spend a week with us, in which time they would do two training courses, agile and DevOps together, and then they would get a final day of workshops and bringing everything together. The learners would then go away with two commercial certifications and a DevOpsGroup Academy diploma. And the Welsh government will be funding 50 percent of the cost of that course for any Welsh SME that takes part.

    The other thing is that we are working with the local universities across Wales to run these boot camps with students as well. So the idea is that we are not watering these down, and creating a boot camp specifically aimed at students. We are giving them the full commercial experience.

    And it also a great opportunity for SMEs to come to the boot camps to meet some really exceptional students that they may think about recruiting at some point down the line. And it’s a great opportunity for the students to work with industry professionals.

    Hartley: So how does an SME get the funding? And how do the boot camps work in practice?

    Harvey: Getting the funding is easy. It’s a case of paying for the course and reclaiming 50 percent of that back. You simply fill out a two-page form, which we can help with, and it means that Welsh startups get a fantastic deal out of it.

    Practically, we have great training facilities in Cardiff. And we have access to similar facilities across Wales and the rest of the UK, for when we take the boot camps on the road. Ultimately we get people together to run through the two training courses and multiple different activities and games.

    And then there’s a day to bring everything together, to take all that learning that you’ve had in the classroom and apply it with some workshop activities or some discussion about how this might help solve some of the challenges you have within your organization. And again, the idea of hosting it here is that we have all these different practitioners who can jump in and out of sessions to offer their advice, as an engineer or as a consultant or from whatever role you can imagine.

    So it really is that next step on from just coming in for a training course. It has the emphasis on accelerated learning, so you tick three boxes with one trip, plus you get all of the networking and the collaboration that comes along with the boot camps as well.

    Initially we’ll pilot the boot camps with DevOps and agile, as a combination. Then ultimately the sky’s the limit, really. There’s a huge potential for technical-based training alongside the DevOps and agile courses. Both in terms of agile working practices and how we deliver this training, this is all too often the neglected part of IT, both at university and at a commercial level.

    — Adam Hartley

  • Fast Pass: Your Ultimate Guide to the Best of Jenkins World

    Fast Pass: Your Ultimate Guide to the Best of Jenkins World

    At the end of the month, Jenkins users and DevOps professionals from around the world will head to San Francisco for the annual Jenkins World conference, taking place Aug. 28-31. The conference lasts four days, but time flies when you’re attending trainings, keynotes, sessions and networking events. To make sure you get the best of everything at Jenkins World, we’ve put together a guide that will ensure you have the most productive and enjoyable experience.

    NOTE: devopsy.kinsta.cloud readers can get 20 percent off registration with the code JWDEVOPSCUST.

    Take the Time to Develop Your Skills

    The first two days of the conference will be full of workshops and training sessions. Regardless of skill level, there are trainings for everyone. Those just getting familiar with Jenkins can attend an “Introduction to Jenkins” training for free and learn how to easily create pipelines while putting in place best practices for continuous integration (CI) and continuous delivery (CD).

    Those a bit farther along their Jenkins journey can attend workshops such as “The Final Mile: Jenkins Pipeline and Patterns for Operations,” where attendees will review patterns of common problems and solutions specific to operations teams in a CD environment , as well as how to create Jenkins pipelines that address the needs of operations.

    Don’t Miss These Essential Sessions

    All attendees should make sure they make it to each of the keynotes, of course! Keynote speakers include Sacha Labourey, CEO of CloudBees; Kohsuke Kawaguchi, founder of the Jenkins project; and Jez Humble, CTO at DevOps Research and Assessment LLC.

    In addition to top-notch keynote speakers, there are a number of DevOps professionals you’ll want to hear from while at the show. Try to attend at least one of these sessions:

    Keep an Eye Out For …

    Make sure you listen in to find out who the winners are of the first annual Jenkins World Awards Program. There are two awards tracks: Jenkins Community Awards and CloudBees Innovation Awards. Each track has several categories including Jenkins Contributor Award, DevOps Automation Excellence Award and more. Winners will be announced Thursday, Aug. 31, at the show.

    You’ll also want to stop by the sponsor expo hall to check out dozens of great vendors. As with any good conference, there will be plenty of swag passed out. Exhibitors will include GitHub, BlazeMeter, Docker, JFrog, Fugue, Sonatype and others. Don’t miss out on taking a photo with the famous Jenkins butler at the CloudBees booth!

    Can’t Forget to Network

    With so many great sessions to attend, don’t forget to make time for networking events. It would be a waste to not take advantage of dedicated networking time to speak with experts and peers who have likely dealt with some of the challenges your organization may be facing. There will be several networking opportunities, including a reception Aug. 30 sponsored by CA BlazeMeter. Or if you’re looking for ways to stay active, attend a scheduled walk or yoga class.

    If you can check off all of the above activities, you’re bound to leave Jenkins World a better professional! Make a checklist at the start of the conference to ensure you hit all the events and sessions you’re most excited for.

    If you haven’t registered yet, there’s still time! Use the promotional code JWDEVOPSCUST for 20 percent off.

    About the Author / André Pino

    André brings more than 20 years of experience in high technology marketing and communications to his role as vice president of marketing at CloudBees. He has experience in several enterprise software markets including application development tools, middleware, manufacturing and supply chain, enterprise search and software quality and testing tools. André has particular expertise in working with the executive teams of enterprise software companies to create unique competitive positioning, build pipeline and establish sustainable market leadership. Prior to joining CloudBees, he served as principal analyst serving technology marketers at Forrester Research. He has also held a number of senior management positions in marketing and communications with companies such as Segue Software, Hewlett-Packard, Unisys Corp. and Bluestone Software. André holds a BS from Eastern University.

  • Jenkins World: Q&A with CloudBees CEO Sacha Labourey

    Jenkins World: Q&A with CloudBees CEO Sacha Labourey

     The Jenkins Community and DevOps professionals around the world are excited for Jenkins World, coming up in just a month, Aug. 28-31 in San Francisco. CloudBees, the hub of enterprise Jenkins and DevOps, is the lead organizer and premier sponsor of the event. We sat down with CloudBees CEO Sacha Labourey to discuss everything Jenkins World.

    NOTE: If you haven’t registered yet, there is still time! devopsy.kinsta.cloud readers can register now with the code JWDEVOPSCUST and get 20 percent off.

    Q: How has Jenkins World evolved since its inception?

    A: It’s been quite the journey since the beginning of Jenkins World. The very first Jenkins World was back in 2011. We had 200 people attending and we were extremely proud of that. The Jenkins project was still new, as it had just changed its name in 2011, so we were excited to see the community already coming together. Fast forward to 2017 and we’re expecting about 2,000 attendees at this year’s event. We’ve grown 10x since the first show and even from last year to this year we’re expecting almost 50 percent more attendees. It’s been great watching the conference mature and grow over the years. 2017 will be our best show yet!

    Q: What’s new at Jenkins World this year?

    A: This year we’re expanding everything, covering a wide range of topics including DevOps culture, process design, automated testing, performance measurement, security, leadership and more. We’ve added a welcome reception and evening event in the expo hall so attendees have more opportunities to network and learn from each other.

    Additionally, we’ll be kicking off the first-ever annual Jenkins World Awards. These awards recognize the achievements of CD innovators and Jenkins contributors from around the world. There are two award tracks: Jenkins Community Awards and CloudBees Innovation Awards. Winners in each track will be featured at Jenkins World.

    Q: What can attendees expect from the keynotes?

    A: We have a great lineup of keynotes this year, including myself! My keynote will be a state of the union that looks at what’s happened in the last year, what worked, what didn’t work and what we’ve learned from it. Stemming from that I’ll also offer a vision for the future. This will be actionable, and practical—something we can truly act on. I’m excited to say that there will be some significant announcements throughout the week as well.

    Kohsuke Kawaguchi will also be keynoting. His keynote is always excellent. He’ll offer a state of the union from the Jenkins community angle. He’ll go over the evolution of the Jenkins project and run through the latest numbers. It’s such a pleasure to watch him on stage each year; his talks are always exciting.

    We’re also thrilled that Jez Humble will be keynoting this year. He literally wrote the book on DevOps, so if you’re looking to learn about DevOps, he’s the man you want to hear. He’ll be discussing the DevOps market, challenges, opportunities, the evolving requirements and needs of DevOps professionals and more.

    Q: What advice do you have for first-time attendees?

    A: My advice is: Take advantage of the trainings, workshops and certification opportunities. Last year, workshops and training were a huge success, so we’re offering even more this year. It’s a great way to further your career. It’s very hands-on and provides an opportunity to show tangible results of how the conference helps you improve your skills and ultimately helps your career.

    Also, make sure to network with fellow professionals. It’s the perfect time to find out how others are approaching their projects, what challenges they faced and how they’ve overcome them. It’s such a great community of professionals to learn from.

    Q: Are there any sessions you recommend?

    A: I’d certainly recommend checking out some of the specialized vertical sessions. For example, we’ll have a number of sessions that focus on the financial services industry with speakers from Capital One, PayPal and more.

    We’ll also have some great DevSecOps presentations. It’s a very hot topic and is increasingly important in DevOps. I’d highly recommend attendees get to at least one of these sessions.

    Finally, there will be several sessions focused on testing—which often adds the most friction to delivery pipelines. These sessions will prove really helpful for attendees looking to enhance their testing processes.

    There you have it! This year’s show is bound to be bigger and better than ever before. Register now with your 20 percent off code: JWDEVOPSCUST.

    — Alan Shimel