
Sign up to save your podcasts
Or


Debbie Madden has built five companies from the ground up, is a lead generation istructor at General Assembly, and a sought after public speaker and writer, appearing in The Wall Street Journal, Forbes, Fox Business TV, the HuffingtonPost, Inc. Magazine, and more. Prior to Stride, Debbie was the CEO of Cyrus Innovation, an Agile software development consulting firm, which she grew Cyrus into a 60-person, multimillion-dollar, five-time Inc. 5000 Fastest Growing Private Companies winner, and Crain’s NY Best Place to Work.
How does a team realize their best?
Improve in small steps, not trying to change the world overnight
Expand on strengths
Identify risks, past success, factors in control
Make the process of software development more reliable
Honesty
What are your goals, are they realistic?
Adding value is making product better
People’s opinions are based on past life experiences
Risk
Decisive — set tripwires
“Liftoff” meeting — Diana Larson, Liftoff
Create working agreements, risk assessment
Proactively monitor risks
Tools to help stay aligned with principles and priorities
Have deadlines for action items and follow up
3 things you will stop doing in next 30 days to make room to do this?
Categorize how you spend your time
Other episodes mentioned: Ken J
Jessica Barnett is a Product Manager at a startup called Medivo. At Medivo, they’ve adopted Trello to organize just about everything, including their retrospectives. After seeing the positive impact of retros, there was company-wide adoption, starting with the c-suite. Not only has the company embraced some agile practices, the team has been able to influence business to reduce overwhelm, staying aligned with their top priorities.
Trello Retrospectives
See Jess’ post detailing their process
Its the one time the whole team is focused on improving our lives
Influencing Business
Retros pulled across company, starting with c-suite
Creating visibility on overwhelm
Many different ways to tell the same story
How can we ensure if this is the most important thing it is what we are focused on?
What worked
Demonstrated velocity improvements with focused efforts
Pushed back on requests
Gained clarity on top priorities
If you want us to do great work, this is the way we’re going to do it
Needed support to say “no”
VP of Technology saying “you present the facts, you drive home principles and I’ll make sure it goes okay” (and following through by defending the team)
Contract between business and technology agreeing to use Agile to manage development
Performance connected to celebration and investment in your people
If you believe in your principles, find ways, experiment with ways that you can communicate those principles and make it happen.
John Shiple — Freelance CTO, technology advisor — triages businesses, help business scale, launches new businesses. John's been in technology over 20 years and loves building websites.
In Part 2 of this interview, John and I continue our discussion about founders and startups needing (or not needing) CTOs. Red flags to watch out for (both the founder and the CTO) as well as some stories and philosophies based on John's experiences and expertise.
Part 1 can be found here.
John Shiple — Freelance CTO, technology advisor — triages businesses, help businesses scale, and launches new businesses. He's been in technology over 20 years and loves building internet sites.
In Part 1 of this interview, John and I discuss important topics for non-technical Founders to consider including recruiting challenges, expressing ideas, and the importance of a technical leader. This is a great episode for both founders and technical leaders to get an understanding of common challenges and misalignments.
Notes from Interview
Collection of Videos about CTOs, recuriting and startups by John (created by DocStoc)
Common weaknesses (business side)
miscommunication on product needs
lack of background in technology
fragile relationships between business and technology
technology is the least important - you need to have the right people building the right things
Recruiting Help
more challenging than other domains
if you have a good friend from college that knows CS, get them onboard
every techie is working and if they aren’t its because they are choosing not to
John will be teaching a class at GA on How to be a CTO (this November in LA)
Joanna Clay is a reporter for The Orange County Register. Previously she was working with the Los Angeles Register and covered the West Side with a focus on tech and the Silicon Beach phenomena. In this episode we discuss her takeaways and observations in creating the article on Why there aren’t more women in the tech industry (pdf version).
Interview highlights
Article Summary
1. Companies need to advertise opportunities in a way that is appealing to women
2. Girls need messaging from a young age that encourages exploration into engineering
3. Engineering needs to be discussed more in the media and schools
Projects Creating Shifts
Hopscotch — Getting girls excited about tech at young ages
Changing the Conversation -- Initiative to change the way we speak about engineering
Girls Explore Engineering
Santa Monica Youth Tech Program
VC needs more women too!
oasis summit -- vow to be chic
Jesse Draper and Valley Girl Ventures
Have a good story about tech on the west side? Contact Joanna
Past interviews mentioned on the show:
Josh Bigelow
Luke Melia
Ryan Janssen has been creating and leading companies for the last 20 years. His latest venture, Collectively, aims to improve the way people work.
Ryan and Wendy discuss the lonely entrepreneuer, the challenges around working by yourself as well as how his company, Collectively, is evolving. It is a fun conversation for anyone who has worked by themselves, started a company or likes the Borg.
Notes from the Interview
lonely entrepreneur
corporate culture sucks…talk in a way, dress in a way, interact in a way with people that just isn’t you
companies provide colleagues
socially isolated environment
bipolar role — company cheerleader and risk mitigator
challenges
we’re all afraid to get our stuff in front of people
rabbit hole w/o outside opinions
fear inhibits success
evolve based on experiments
Ken Judy has twenty years experience in development and over a decade of experience leading and creating agile teams. Currently he is VP of Technology at Simon & Schuster, and lives in Brooklyn with his wife and daughter.
This is a great episode for technical leaders and team members to understand how to create value on their technical team beyond pushing tickets. We also discuss how the day to day actions and behaviors of leadership impact the decisions and values of the team.
Notes from Interview
Improv Theater Takeaways
in theater people have a good sense of the lifecycle
adjusting expectations based on constraints and timeframe
constraints support creativity
you can’t get performance from an actor without interacting with the actor
Typical Environments
developers are creating the product and often don’t have say in what they are crafting
kill yourself to get to date, not make the date and then its arbitrary, so they just set another date
only way to have accountability is to have a date
Team Dynamics
different personalities combine
having right environment that attracts the right talent takes a long time
i wanted a way of working that allowed us as a small team to take advantage our our individual strengths and not be victim of individual weaknesses
Leadership
developers are achieving what their company wants them to achieve
they will do what your values/actions tell them you want
people say they value quality, but their day to day actions and priority do not
if you cannot have collaboration around features, you will automatically sacrifice quality
Valuing Quality
model through collaboration
humility from the stakeholders
listen to risk
what you want to achieve -- not how
creative ways of measuring value
Antipatterns
developers are there to code and efficiency is about passing off tickets
master/slave paradigm
by the time it gets into debs hands, the business has already made too many decisions that limit impact devs can have on limiting work and creativity
its all about how many people are on something and not who they are
Where to start
a conversation with business, product and developer is most efficient conversation
once you have that practice internal, build relationships with outsiders
often time people asking for work are not in technology and developers are not domain experts
coding is meaningless without understanding the problem at hand
The value is in the team
companies that think they are agile and constantly reform team
team reforms every time it changes
small group who know/trust each other, needs to be reestablished if even one person changes
core talent of development team is problem solving
Fallacies
there is value in variety, can lead to a new spark of creativity and excitement
people will roll on/off team, that is life
never have to worry - oh no team has been together too long, i need to shake things up
Agile
agile is not about delivering more stuff, its about delivering more value
accomplishment comes from focus on what really matters
achieve outcome with least amount of waste.
you need to understand success on small scale to know what success looks like on large scale
You get what you ask for
devs close stories when it meets the letter of what you ask for
schedule pressure makes it too easy to not get it "done done"
if you criticize velocity, your team will increase velocity, but most likely deliver less value
Read more of Ken's thoughts and experiences on his blog.
How does your team stack up? Ask the right questions.
Luke Melia is a software developer, co-founder/CTO of Yapp who loves building great teams and communities. Luke helped create the first GORUCO and the Ember.js community in NYC.
In this podcast, Luke discusses Yapp’s early adoption of Ember.js, and its impact on revenue, community and recruiting. We dive into building community, unique takeaways about Ruby, and the many benefits of community. This is a great talk for people interested in speaking, teams who need to grow, and leaders who want to infuse a vision into their culture.
Ember History
Adopted Ember from Sproutcore
Ember consulting funds Yapp
Ember.js meeting up NYC has over 1100 people
Ruby is Unique Community
No big corp behind community, the driving force was individual
Motivation, style, stems from roots
Community takes responsibility to fix problems
Lessons from Ruby Community
Matz is nice and so we are nice
People talking about it made it true
Took into Ember — together we help folks climb the learning curve
After a while you are saying the same words and instead of vision it becomes true
Impact of Community on Hiring
First crack at folks as they come onto the market
Apprenticeship programs
Find talent, be attractive to talent
Talented devs don’t come onto the market… they reach out to a few friends and have a new job
Other Ramblings
Lightening talk great introduction to public speaking
Differences between Silicon Beach and Silicon Alley
Historian Role
Community Builder? Ping @lukemelia on twitter
Tweet @embernyc to find out where they are going for drinks the evening of a meetup
Dan Mezick is a management consultant, author & keynote speaker. His work includes The Culture Game, a book based on five years of experience coaching 119 Agile teams across 25 different organizations. He is also the cultivator of Open Space Agile Adoption.
This interview is a continuation of Part I
Notes from Interview
After Open Space
Proceedings are the beginning
Adoption is learning through experimentation, inspected at next open space
Stuart Kauffman, Santa Fe Institute — The Adjacent Possible (http://edge.org/conversation/the-adjacent-possible)
Coaching Change
Coaching + experimentation => learning can take place
Experiments make a space for learning
Cannot inflict help
Power of Invitation
Pull out of comfort zone rather than push through invitation
Frame it like a party
Let the teams pull changes instead of pushing on them
Play
A lot of work is really serious play
The opposite of work is not play
Solving problems doesn’t have to be heavy process
Open to Failure
Games dissolve tension, make room for love
We like to fail fast, but are uncomfortable with vulnerability
Mandated collaboration is ultimate oxymoron
Unwilling Participants
Reduce commitment by 1/2 until they willing to try
Create opportunities to try, not mandated
Disengagement Epidemic — Pushing Mindset
We pull work in Agile, but routinely push agile without teams consent
Most people unhappy/disengaged with work
Engagement is associated with a sense of control and belonging
Improving Velocity
Great work possible for any team
Make the team the genius instead of hiring geniuses
Genius Teams — McCarthy Project (http://www.mccarthyshow.com/aboutus/)
Interpersonal Equity
Substantial asset to team productivity
Energy is created in group from history of the group
Creates lasting friendships, strong networks
Dependency, Autonomy and Mastery
Consulting versus Coaching
Explicit boundaries needed
Steven ‘Doc’ List
35 years in software development, business owner, facilitator, agile coach
Team and People
technical practices take you so far
Teams that work well together more productive
Learn how a team collaborates by observing
choice of words indicate culture and mindset
Red Flags
Difference between facilitated and run
meetings should be multidirectional, conversation — purpose, learning
we’re all in this together, how do we all contribute
Facilitation Antipatterns
Gladiator, Benevolent Dictator, Superhero
champion - great deal of responsibility for success or failure
nice people in bad positions
culture of blame, a culture of fault, a culture of heroism
Role of Coaches
coaches role is teaching
rather than wrong/bad, asking questions
telling is not a good way for influence
balance guidance, question and strong suggestion
take it to the team
Help the Disenfranchised
stickies on the wall
give people tools/ways to democratize the process
Agile Retrospectives (http://www.amazon.com/Agile-Retrospectives-Making-Pragmatic-Programmers-ebook/dp/B00B03SRJW/ref=sr_1_1?s=books&ie=UTF8&qid=1406827093&sr=1-1&keywords=Agile+Retrospectives)
I don’t know why it works, but it does so I’m going to do it again!
Language Matters
interpretation of behaviors cause problems
communication is a dance
Non-Violent Communication
Crucial Conversations (http://www.amazon.com/gp/product/0071446524?ie=UTF8&tag=athought-20&linkCode=as2&camp=1789&creative=9325&creativeASIN=0071446524)
Ask yourself, why would a rational, reasonable, decent human being do that?
Dangerous Words
“can’t” “made” “feel” “should”
Superteams (http://www.amazon.com/Superteams-How-Take-Your-Team/dp/0670921483)
Practice
think about your words
judgements are not feelings
make an effort to make a change
Contact
Doc List https://twitter.com/athought
His Recommending Reading http://www.doclist.me/reading/
Check out his blog (http://www.doclist.me/) for more about patterns and anti patterns
From the publisher's feed