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
“We’re really struggling with the Product Owner concept, and many of our Scrumteams just don’t feel very productive.” The company had several vertical markets, with a Scrumteam of about ten people assigned to each market. Each market had a Product Manager, a traditional role found in most product companies.
When it comes to organising engineeringteams, a popular view has been to organise your teams based on either Spotify's agile model (i.e. squads, chapters, tribes, and guilds) or simply follow Amazon's two-pizza team model. It is one of the ways you can organise your engineeringteams in a retail environment.
He had come on a ten-day trip to India to select an Indian offshore company to be his Agile provider for software development services. He had already met with many top software providers to learn about their ability to deliver high-quality software and demonstrate Agile software development capabilities. It’s not magic: it’s Agile.
This is a pre-release excerpt of The Art of Agile Development, Second Edition , to be published by O’Reilly in 2021. Visit the Second Edition home page for information about the open development process, additional excerpts, and more. For a team to be Agile, they need to change their method to reflect the Agile philosophy.
Drawing on his 40 years in the software industry, GeePaw’s solution is to develop a thick culture in which certain standards are established across the industry. How the doubling rate resulted in a lack of leaders that can develop an industry discipline (6:34). Developing a common language of change in the trade (24:24).
In this Perspectives in Engineering interview series, engineering leaders talk about how to build, coach, and scale world-class technology teams. Saminda Wijegunawardena , VP of Engineering at Box, calls this increasing distance “abstraction.” This role doesn’t change whether an engineering org is 5, 500, or 5000 strong.
This is a transcript of my keynote presentation for the Regional Scrum Gathering Tokyo conference on January 8th, 2025. It was September 2023, my CEO was asking me a question, and my position as Vice President of Engineering was less than three months old. Kent Beck concluded , Measure developer productivity? Not possible.
In this episode of Programming Leadership, Marcus and his guest, Rich Mironov, discuss the all too common disconnect between developers and those on the marketing side of organizations. Differences in design principles between product and engineeringmanagement (1:35). How efficient is the team? Transcript.
In this episode of Programming Leadership, Marcus and his guest, Rich Mironov, discuss the all too common disconnect between developers and those on the marketing side of organizations. Differences in design principles between product and engineeringmanagement (1:35). How efficient is the team? Transcript.
And then two years later, I switched to the engineering side of the organization where I currently lead team-building marketing automation solutions, bringing Data Science and Machine Learning to solve these problems for our customers. And we also have dedicated teams to look into some of this. Alfred: Great. Vatsan: Well.
In this episode of Programming Leadership, Marcus and his guest Don Gray enlighten listeners regarding the world of software development, the reasons for implementing software changes and why it’s not as easy as people may think. Software development is not linear and not deterministic. Show Notes. Change is complex. Transcript.
We organize all of the trending information in your field so you don't have to. Join 49,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