Hiring a ruby on rails developer

One of our team is moving on. So we’re looking to hire one full-time, experienced developer.

At Simon & Schuster, we’ve created a small, collaborative team where people can do their best, learn in a collegial environment and get home at a reasonable hour. We work at a sustainable pace because after five years as a Ruby on Rails team we know the value of staying current, refactoring our codebase, and cleaning up tech debt.

We pair, we test drive, we retrospect, and we work as a single team with our product owners. If you want to work on a team that really does these things, contact us.

Scrum/XP/Agile team in midtown Manhattan looking for an experienced Rubyist or experienced Java/C# developer interested in learning Ruby. We are an established, six developer Scrum/XP team. We have a dedicated scrum master and we collaborate closely with our product team

Apply via StackOverflow

No recruiters, please.

Presentation: Agile Values, Innovation and the Shortage of Women Software Developers

Presentation notes: http://khj.me/KLKm0u


Judy, K.H.; , “Agile Values, Innovation and the Shortage of Women Software Developers,” System Science (HICSS), 2012 45th Hawaii International Conference on , vol., no., pp.5279-5288, 4-7 Jan. 2012

doi: 10.1109/HICSS.2012.92

Abstract: The percentage of women software developers in the U.S. has declined from 42% in 1987 to less than 25% today. This is in a software/internet marketplace where women are online in equal numbers to men, directly or indirectly influence 61% of consumer electronics purchases, generate 58% of online dollars, and represent 42% of active gamers. Women avoid careers in software due to hostile environments, unsustainable pace, diminished sense of purpose, disadvantages in pay, and lack of advancement, peers or mentors. Agile Software Development is founded upon values that challenge such dysfunction in order to build self-organizing, collaborative and highly productive teams. In a high functioning Agile practice, developers engage each other, product owners and sponsors in a shared concern for quality, predictability and meeting the needs of end users. Can Agile values and practice drive changes in the workplace to better attract and retain women software developers?

URL: http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=6149534&isnumber=6148595

Innovation and collective product ownership (Agile 2007 presentation)

Jeff Patton reminded me about the product work my old Oxygen team did in 2006-2007. I dug out this presentation and accompanying paper that Ilio Krumins-Beens and I prepared for Agile 2007.

Our work anticipated the change in the Scrum Guide to consider the product owner as part of the team.

We developed an original windows software application using Scrum/XP with an onsite product owner and UX designer.

We evolved the product experience validating our assumptions using user personas and both informal and formal usability testing.

We released the product as a free Beta by the time of this presentation in 2007 and were working to build a customer base.

The lifecycle of a company (and the larger economy) doesn’t play nice with hopes and intentions. Oxygen was acquired by NBC-Universal before we were able to validate our assumptions.


Judy, K.H.; Krumins-Beens, I.; , “Ript: Innovation and Collective Product Ownership,” AGILE 2007 , vol., no., pp.316, 13-17 Aug. 2007

doi: 10.1109/AGILE.2007.49

Agile’s broad adoption and mediocrity – the fault lies…

I have to admit, I cringe whenever I say “agile” or “scrum” (™?) Even as I practice both every workday and care deeply for the values they represent.

Successful movements take on a cloying “fill me with your knowledge” cast. A perpetual newbie state where new adherents come on faster than existing practitioners have opportunity to develop experience and wisdom.

I really don’t need to have another conversation about how to phrase the first sentence of a user story.

And I definitely feel some of the same heat rising from the attention to lean. Buzz, buzz, kanban, buzz…

But can we blame the thought leaders, the coaches, the industry deriving wealth from a movement for the failings of that movement? Is it the corrupting influence of success or rather broad adoption itself?

I think the latter.

First, let me acknowledge that iterative improvement is a lengthy process and has to start somewhere. That your current state is entirely flawed is a given.

You don’t have to be excellent at what you do at this exact moment to begin improving your own practice and your workplace. A broad swath of not soul killing workplaces is at least as valuable as a small set of shining cities on the hill.

But whatever the starting point, taking on agile practice is dedicating yourself to a mission of fundamentally changing the nature of our work to something both disciplined and highly accountable but also collaborative, creative and sustainable.

And broad adoption means that a lot of people who call themselves “agile” just don’t rise up or even aspire to rise up to that mission.

If you claim you’re doing XP: have 24 hour builds, the developers all work solo and your test coverage is 10% then you’re either at the start of a very long journey (which I deeply admire you for) or you’re lying to yourself and you just plain suck.

If you claim you’re doing Scrum and the developers haven’t talked to a business person in months, can’t articulate what your team achieved in the last month, and you require “stabilization” sprints before you can deploy working code, you are either at the start of a very long journey (which, again, I deeply admire you for) or you’re lying to yourself and you just plain suck.

It’s not one of a thousand consultancies, professional coaches, certification tracks, associations or conferences fault if you suck.

It’s not Jeff Sutherland’s or Ken Schwaber’s fault if you suck. As a matter of fact, they and their peers have done a great deal to give a great many of us a chance at sucking less.

The mentor/mentee relationship is powerful but it’s up to each of us to do our work with courage, integrity and passion. It’s up to each of us to hold our peers to a standard of competence and care.

“The fault, dear Brutus, is not in our stars, But in ourselves, that we are underlings.”

Agile, Scrum and 4DX

Our company is adopting a practice called “The 4 Disciplines of Execution” (4DX). Superficially, it’s goals and techniques are very Scrum-like with a focus on rallying self-directed teams toward a single, important company goal.

Team Scoreboard

Layout of our combined Scrum/4DX team scoreboard

Like Agile, it champions practices but emphasizes values that give those practices reasons for being. 4DX is more focused on outcomes than specifics of performance – which is a nice puzzle piece to slot along side into a lean or XP discipline.

I’m fascinated to watch the course of a top down process change. I’m also wary of what happens when groups that don’t feel an urgent need for change or share the values of team, collaboration, and focus bang their heads into this particular demand.

Still, I am hopeful and excited. After a few years at my company once again championing a team-up Agile adoption, I feel tremors as the rest of the company shifts to meet us.

Part of being lucky is being ready.