This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
My role at Buildium In late 2009 the economy had tanked and I had a newly minted MBA but no real job experience. I was managing a team of 15 and the company had grown to about 140 employees. What they did effectively early on is bring other hugely talented people onto the team before they could afford to pay them their market worth.
The same was true when I ran the People function at a softwaredevelopment consultancy that doubled its headcount to ~100 while reducing attrition from 40% to 5% voluntary in 18 months. The question becomes: “Who do I want on my team—and why?”. A final comment on purpose: It should come from your team.
When deployed correctly, Product Ownership is an invaluable role that provides tactical support to your developmentteam, translates customer value, goals and pain points into product improvements, and leads effective and impactful development sprints. Q: What was your first job? How did you get started as a Product Owner?
If an organization’s founders aren’t designers and don’t come from a background where well-designed products played a key role in their lives, it can often be the last discipline to be brought onboard the team. On a bad day, a lot more of it got thrown away. My responsibility was to build a design team in that new agile way of working.
What does Jeff mean when he says, “the developer first approach is a maturation of the supply chain of software?” How has Jeff seen his original thesis for “developer first” evolve and change with time? What does truly special customer experience look like in the developer first model? * They got going in 2009.
We organize all of the trending information in your field so you don't have to. Join 80,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content