“To some extent Agile isn’t a solved problem.”
“Agile needs to freaking grow up.”
“We need to stop calling it Agile.”
“We need to stop saying Agile makes it easy to go faster.”
“Agile got us going, but DevOps is going to take us where we need to go.”
In the conference rooms of Agile 2016 in Atlanta this week, there was a lot of talk about where Agile is today. At 15 years old, Agile, in one sense, is maturing and going strong. But, even among those who preach it – and make a living from it – there is just a hint of unease when it comes to talking about the future.
Nowhere was this more obvious than during the session “2020: The State of Agile.” Moderated by Jann Thomas, a former developer, with three Agile coaches as panelists, this session was standing room only. But, as the session progressed, more and more people started to leave. The issue, it seemed to me, and in discussion with other attendees later, is that people were looking for a practical road map for Agile’s next few years. They wanted to hear, head on, how to tackle the challenges. What about new technology, what about DevOps, what about the fact that this can be so very difficult to get right?
The panelists were clearly frustrated with Agile’s “reputation” but their solutions were cosmetic in nature. One suggested renaming Agile (“it’s tainted” by folks who couldn’t do it correctly), and then offered up a slew of catch phrases including “bring your femininity to the job,” allow “openness and compassion,” “speak from your heart” and “bring your vulnerability.” At this point, a lot of people were leaving and one man raised his hand and suggested his CEO simply wouldn’t want to hear those things. There was nervous laughter at that.
And when the group did try to get a bit more nitty gritty, they suggested de-coupling Agile from speed of delivery. Don’t focus on faster delivery, focus on “sooner.” Is there really a difference here? They insisted there was but I am still not so certain.
This session left me – and many others I spoke with – feeling deflated. Change is coming, whether it’s via the Internet of Things, the cloud, or DevOps. Change doesn’t have to mean the end of Agile – after all, it’s quite diluted already given the thousands of different ways companies “do” Agile. But in order to roll with change, and grow from it, you need to acknowledge it. Agile needs practical and unfortunately for much of this week what we heard were platitudes.
It is, indeed, time for Agile to grow up and take the next steps.
Developers, slow applications are really not your fault. And I’ve got two examples to prove it.
And in the category of other things you have no control over, it’s time to bring Brexit in to the mix. While obviously the UK leaving the EU isn’t going to slow down your app, it may slow down your app development, particularly if your developers are in the UK. The European Union allows free and easy travel between member nations, something that’s translated in to a lot of software devs from other countries working in London. That’s helped ease the shortage and boost productivity, but things are changing, according to Robert Grimsey, director at UK-based recruitment firm Harvey Nash. “Brexit has created uncertainty,” he said. “We’ve seen it in the lead up to the Referendum, during which demand for recruitment across all roles – including software development – was down. Now that Brexit has been confirmed, our expectation is that demand for permanent software development roles will continue to stay suppressed until there is a greater visibility.”
What could that mean? More contract jobs, for starters, as companies may not want to hire permanent workers. And it could mean a hiccup — or ten — when it comes to development projects.
The bottom line: lots of things are out of your control, like third party apps and political upheaval. At a time when many are tired of hearing how the dev process is at fault, perhaps today we can all take a little (admittedly cold) comfort in the fact that we can actually identify a few of the culprits. It won’t last forever, but for right now we can try to enjoy it.
Yes, you read that title right. Too bad I can’t take credit for the pairing.
Way back when I worked for a daily newspaper, the most exciting times of all were of course the election cycles. The late nights, the meet and greets, the feeling of change in the air…good times.
It’s another election cycle — by all accounts a one of a kind cycle at that — and of course change *is* in the air still. And not just when it comes to politics.
I interviewed Will Evans, chief design officer at Praxis Flow, a couple of weeks ago. He’s a lean development expert, sure, but he’s also a fun and lively interview. I would guess his seminar at QCon was probably a lot of fun.
But Evans will always have a special place in my heart because in this election cycle he brought together two wildly different “things” and actually made it work: DevOps and Bernie Sanders.
“Imagine Bernie Sanders is the DevOps of politics — fresh ideas but fundamentally not changing the entire system,” Evans said. “People are idealists in DevOps. If Bernie can change the platform and shift the Democratic party to the left 5% that is progress but not perfection and DevOps is the same.”
Evans thinks the biggest problem in the software development arena is that people aren’t engaged and are at risk of spending their time doing things that don’t matter. DevOps, he believes, can be that change, but like Sanders, you have to see it as a process and and not an end result. “The promise of DevOps is to move things, to make things 1% better next year. That is meaningful. This is a long haul with a lot of hard work and we’re not going to have change overnight.”
Can we afford to be patient? I hope so.
Tell me how you think software development and the election cycle are linked.
Ask any application-development decision maker or programmer: Emerging technologies force enterprise IT shops to rethink not just which new products and services to adopt, but even more importantly, the very nature of how they do their jobs. For this reason, TechTarget’s expanding its coverage of IT operations with the launch of SearchITOperations.com.
Our long-standing attention to core application development technologies and buying trends — such as development ALM and app containers — will not change on the TechTarget coding and software websites you already read. Rather, through the new SearchITOperations, we recognize the cultural and technological transformation underway as IT operations and application development more closely collaborate to heighten their enterprise’s ability to respond to market changes.
Reaching into 2020
Looking out over the next three to five years, strategic IT shops will need to move beyond cost savings or avoidance, marked by silos and limited collaboration, to thrive. All aim for stable, flexible operations that are custom fitted to the internal landscape, corporate goals and business outcomes of that enterprise.
For many IT shops, the desire to facilitate shorter application release cycles without outages and mistakes means reordering staff, acquiring new skills and choosing from a plethora of new tools to automate tasks.
The new site is dedicated to the news, features, how-to tips and other expert content that enables IT operations pros to manage new application architectures and faster release cycles, along with the feedback loop concept promoted by DevOps. From our view, these tie-ins with AppDev teams are clear and important.
As always, our readers can expect unbiased technical information as they evaluate new tools, learn additional skills and plan tomorrow’s IT operations.
We hope you’ll check out the new resources on SearchITOperations, and we thank you for your continued loyalty to, and readership of, SearchSoftwareQuality.
My recent story on the surprise skills gap — writing, public speaking, communication and most decidedly NOT tech skills — has me wondering what it means to be the ideal employee. The term “well-rounded” is tossed around a lot, but what does that actually mean when it comes to testers and developers?
I went to a liberal arts college and, all right, I’ll admit I was an ENGLISH major. And not just any old English major — my degree was in 19th C. British Lit. Yes, my father was certain I would never get a job with a degree like that. He was a CPA and his view was that college was supposed to give you a marketable skill or, even better, skills. I obviously didn’t get “skills” but I did get an education.
That was a million years ago, and the world has changed a lot. Just this week I had a reader mention that he literally keeps his developers “locked in a back room” because they are completely unable to communicate — orally, or by email — with his customers in any way that resembles “standard” English. I did not get the sense that his developers were non-native English speakers; instead, it seems they just don’t have good communication skills, which of course brings me back to that skills gap.
So, to be an ideal developer or tester today you need: tech skills, of course, but you need to be able to write, speak and interact comfortably with customers and business people, and then you may need that “extra” something that involves, say, industry experience. That’s what Matt Sigelman, CEO of research firm Burning Glass, refers to as “hybrid skills.”
In other words, I think the bar is getting set at a higher and higher level as time goes on. There are straightforward solutions if you have an employee with insufficient tech skills; but Dale Carnegie and The Toastmasters aren’t exactly household names any more (click on the links if you actually don’t know who/what they are!) and as far as hybrid skills go, a hybrid developer creates him/herself by choice. The employer doesn’t have much to say about that.
So how do we solve that skills gap? Does your company have a strategy that’s worked? Or do you think the problem is overblown? I’d like to hear what you think.
Suddenly, in mid April 2016, everyone, and I do mean everyone, is talking about DevOps. They’re talking about Agile, too, of course, but unless I’m imagining things, it’s DevOps that seems to have captured everyone’s attention.
Last I looked, DevOps adoption was hovering at a (more than likely optimistic) 20% or so in mostly companies that self-identified as digital disrupters (in a survey of 1442). But now…it’s ALM and DevOps, it’s DevOps and security, it’s DevOps DevOps, Devops, oh, and Agile too.
So when did Agile become so last week? SearchSoftwareQuality columnist Jenn Lent, in her end of 2015 column, predicted this might be the year when Agile actually grows up. Seems it might have grown up so quickly that’s it’s morphing in to that next thing.
Is this bandwagon jumping, or is this real? I asked the last CEO I interviewed, who is rolling out a new product aimed at the DevOps market, just what kinds of companies he thought were going whole hog for DevOps. His answer: large companies and startups. Hmmm…those are the same kinds of companies still doing — and working on — Agile.
Another source I talked to a few months back was actually laughing about DevOps. To paraphrase, he said he felt Agile had already upset the apple cart for testers and developers and asking them now to take the HUGE step and embrace DevOps? Crazy talk.
And then there’s the CEO of Shippable who didn’t hold back…he straight up hated developers. Until he was one. And he still thinks the way DevOps is implemented is ridiculous. He calls it a whole “Kumbayah” thing.
But, he’s also got a product focused on making DevOps easier to implement, so he obviously believes in the concept.
So let me ask you — is the DevOps train coming by your town? And what’s happening with Agile while that happens?
It feels like change is coming. What do you think?
According to a new survey from NGINX, our apps are performing very badly indeed. And perhaps what’s worse news is that a whole lot of companies really aren’t doing anything about it.
NGINX did an in-depth survey of 1800 IT professionals on a variety of topics and it turned out there were several surprises, according to Peter Guagenti, chief marketing officer of the company. He said he was very surprised to see how widespread use of containers and microservices were (close to 2/3 surveyed were either already using or seriously exploring containers and nearly the same percentage was true for microservices).
But what absolutely shocked him and his team was the data on performance. According to the survey, app performance was a significant issue for 75% of respondents — they reported their app was either somewhat or extremely slow. Ok, that’s not good. But what’s worse was the fact that one-third of survey takers said their companies were doing absolutely nothing about it. Wow, nothing? (If you don’t want to be one of those ignoring performance, here are 19 ways to make your pages load faster.)
We know that slow applications cost companies tens of thousands of dollars, at least, in lost revenue as users get fed up and head to a competitor or just give up in general. “Not paying attention to this is the modern day equivalent of not paying attention to customer service,” Guagenti said.
On one hand, Guagenti said he can empathize. “What’s really going on here is the constant push-pull. Most organizations are understaffed. They need to build new features and the entire process is targeted at creating new features and not maintenance or performance tuning.” What ends up happening, he explained, is that companies become unwilling to go backwards.
And that’s how apps end up performing badly. What do you think companies need to do to fix this?
The senior site reliability engineer certainly has his work cut out for him. Uber is in 400 cities around the world, with more than 1 million drivers and just recently has gotten in to food delivery in addition to its normal ride service.
I was paying even more attention than usual because, as an attendee at the Fluent Conference in San Francisco, I wasn’t just a journalist. I was an Uber customer.
So while Hughes-Croucher talked, I was thinking about my first Uber ride, which, honestly, went off without a hitch. The pleasant driver arrived two minutes after I placed the request, and it was a restful few moments during a busy business trip.
Hughes-Croucher would certainly have approved because that’s the goal, of course, despite how fast the company is growing. “When everything’s exponential there’s no opportunity to be wasteful,” he said. “You have to find things that are going to make an impact. Reliability and performance are critical. If our systems are down those people can’t work and you can’t get a ride.”
Hmm….I really was going to need another ride soon. Hopefully Hughes-Croucher had me covered. He focused his talk on the importance of detecting bad releases, having fast and efficient rollback and mitigation and making sure there is always performance reliability.
I thought about that later in the day, as I requested another Uber, only to get a “network unavailable” message. Uh-oh. Another try hooked me up with a driver, but he had to cancel the trip because he was pulled over by a cop on the way to picking me up.
That’s not something I can blame on Hughes-Croucher, whose attention to detail is impressive but even he can’t control traffic cops. What he is trying to control, though, is time. His strategy, though complex to implement perhaps, is beautiful in its simplicity. He advocates only rolling out a 5% change and then watching that rollout like a hawk. If there’s an issue, it’s instantly rolled-back and the only “hit” to performance is really to the developer’s productivity and not the customer’s. At least in theory, this makes a lot of sense to me.
During my last Uber ride, I did what I always do and asked how the driver liked his job. He does, very much, but he’s about to radically reduce his hours. Why? He’s decided to go to school to become a software tester.
I let him know Hughes-Croucher (firstname.lastname@example.org) is hiring.
There were plenty of wow moments as IT leaders revealed new software, space and robotics technologies at the 2016 Lesbians Who Tech (LWT) Summit. The biggest surprise, however, was a speaker’s revelation about 1950s’ tech culture. During the main keynote, former IBM Senior Systems Programmer Edie Windsor corrected the widely-held assumption that she was one of the few women computer pros at IBM in the 1950s and 1960s. Indeed, “about a third” of her programmer colleagues were women, she said.
I was certainly surprised. In this post, I’ll share more of this LWT Summit’s revelatory and funny moments, as well as what I learned about software and hardware engineers’ efforts to close the gender and minority gap in IT hiring.
Seeing women and minorities in technical positions was rare in late 1980s, when I became a tech journalist. For a couple of decades, I often was the only woman or one of a handful of women at tech meetups and in session rooms at IT conferences. So, I haven’t been surprised by reports that the number of women in the U.S. IT workforce dropped from 35% percent in 1990 to 26% in 2013. In the past couple of years, I’ve seen the ratio improve … but not a lot.
Thanks to these reports, bad press and diversity activism, many tech companies are making an effort to give more positions to women and minorities, said LWT founder Leanne Pittsford. So far, their follow-through hasn’t been impressive. She urged Summit attendees to increase their diversity activism in her presentation, titled “Take a F@!#NG Risk.”
“We need to take big risks. Without risk there is no progress,” Pittsford said. “There will always be more white, straight, CIS men in power until there is not.”
The opportunities in diversity activism are very, well, diverse. For example, the victory of Edie Windsor’s Supreme Court case against DOMA (U.S. Defense of Marriage Act) led to advances in gay marriage rights. Many 2016 LWT Summit-San Francisco speakers, including Hackathon session leader Kate Jefferson, work with Women in STEM groups, providing tech education. Apple VP Tara Bunch – who spoke about personal communication – is active in the workplace equality group, Out and Equal. Speaker Caitlin E Kalinowski, Oculus Head of Product Design Engineering, is on the board of wogrammer, which spotlights the careers of successful women engineers.
Diversity activism must also fight workplace and societal hostility toward women, minorities and LGBT people, Pittsford said. Join in working toward a world, she said, “where no one can lose their job because of their sexual or gender identity.” That discrimination still exists. In most U.S. states, laws allow employers to fire or not hire LGBT employees, in spite of the protections legislated by the U.S. Civil Rights Law of 1964.
At the Summit, Windsor confided that she had to remain closeted during all of her tech career, though she was out in her social life. “I lied a lot,” she said. In 1975, she retired from IBM to devote herself to LGBT activism.
While there was plenty of straight talk about the lousy state of diversity in tech, there was no male-bashing. TechCrunch reporter Megan Rose Dickey’s presentation, “The Kinsey Scale for Diversity,” is an example of the good-humored attitude prevalent there.
Dickey talked about the media brouhaha that followed Twitter hiring a white male diversity chief. That was Jeremy Siminoff, who held a similar role at Apple. Dickey wrote a pro-Siminoff article about the hire, noting that he is gay. On Dickey’s Kinsey Scale for Diversity, Siminoff gets a point for being gay. So, he’s not at the bottom of the diversity scale. Pittsford, who is white, only got two points for being a woman and a lesbian. Dickey ranked herself higher, because she’s African-American, lesbian and a woman. And so she continued to the point of near-absurdity.
Dickey’s smart, tongue-in-cheek presentation was typical of the day’s presentations. I’ve never laughed so much at a tech conference.
What matters most to you? A big paycheck? A job that is going to make the world better? Or an environment that’s not particularly stressful?
Apparently you do have a choice. According to a brand new survey of 18 large high tech companies from PayScale Human Capital, tech workers today are mostly young, white and male, none of which is surprising. But what might surprise you is that working at Facebook isn’t particularly stressful – just 44% say they’re tense while on the job – while 92% of employees at SpaceX report their jobs make the world a better place.
But of course there are trade-offs. SpaceX employees also say their jobs are the most stressful, and at $78,500, their paychecks are among the lowest in the early career stage. Facebook, on the other hand, is apparently the most satisfying place to work – 96% percent of those surveyed rated it as gratifying. Of course, Facebook is also filled with young people and perhaps they’re happier? The median age of a FB employee is 29.
At more established Hewlett-Packard, the median employee age is 38 (the highest in the survey). Interestingly, HP also has the lowest early career salary, at $65,400. But that doesn’t seem to deter people; HP employees are some of the most experienced and tend to stay around (the median number of years with the company is six.)
Wondering where the women are? eBay has the highest percentage of female employees at 43%, followed by LinkedIn, Samsung and Facebook. Least likely to employ a woman is SpaceX where only 14% of workers are female.
Of course, if it does come down to a paycheck for you, you’ll want to choose LinkedIn, where mid-career median pay was $159,600, or Salesforce or Google, where those paychecks were still over the $150k mark.
Want to know even more about how your job and salary compare the rest of the world? Take the PayScale Salary Survey.