Derik Whittaker

Syndication

News


Images in this post missing? We recently lost them in a site migration. We're working to restore these as you read this. Should you need an image in an emergency, please contact us at imagehelp@codebetter.com
KaizenConf - Open Communication, Resistance to Change, Going with the Staus quo w/ reference to various team roles

Another session that I sat in on today was "Open communication, Resistance to change, Going with the status quo with reference to the various roles on the team "

If I could wrap up the entire session in a phrase it would be the following:

When your team feels empowerment and has passion they will be successful 

Below are my notes, sorry they are not in a long descriptive form, but they are notes :)

Quotes:

The product champion doesn't figure out what the market wants, but brings the team to the customer
Without a good leader, or a champion of the team your team is doomed to fail
Quailty is building a substainable releationship
the value of value is realitive worth
When you do not have the fear of being fired you can become more open

Questions:

  1. What are the barries to opening communication
    - Management/customer sees the release cycle/process as a tax
  2. How are we defining Continous Improvement?
    - taking notices of our process our, release cycle
    - balancing various items like maintainability, without over engineering our product
  3. What is value????
    - this means differnt things to different people
    - means that someone will always be unhappy
    - operations has more work with more installs -- they are unhappy
    - developers have have more pressure if they have more work load
    - one persons pain is another persons pleasure
  4. How do we make change when we are capiable of influincing change, but not the permissionr
    - start local
    - start small
    - hope your ideals spread
  5. How do we move from me to we
    - get buy in from all on the team goal
    - get ownership
    - have pride/passion
  6. How do we get a team to become engaged or passionate
    - ownership
    - self correction, self moderation
    - foster that the project will be a success
    - stay positive
  7. 4 areas of improvement
    - improvement of skills on the team
    - improvement of the purpose of the product
    - improvement of the process
    - improvement of the releationships

Till next time,


Posted 11-01-2008 3:20 PM by Derik Whittaker
Filed under:

[Advertisement]

Comments

Derik Whittaker wrote KaizenConf Wrap Up -- What an Exhausting Learning Experience
on 11-02-2008 7:53 PM

Well, that does it for this years KaizenConf . I can honestly say that I had a great time, I met some

Community Blogs wrote KaizenConf Wrap Up -- What an Exhausting Learning Experience
on 11-02-2008 8:52 PM

Well, that does it for this years KaizenConf . I can honestly say that I had a great time, I met some

DotNetKicks.com wrote KaizenConf - Open Communication, Resistance to Change, Going with the
on 11-07-2008 9:46 AM

You've been kicked (a good thing) - Trackback from DotNetKicks.com

About The CodeBetter.Com Blog Network
CodeBetter.Com FAQ

Our Mission

Advertisers should contact Brendan

Subscribe
Google Reader or Homepage

del.icio.us CodeBetter.com Latest Items
Add to My Yahoo!
Subscribe with Bloglines
Subscribe in NewsGator Online
Subscribe with myFeedster
Add to My AOL
Furl CodeBetter.com Latest Items
Subscribe in Rojo

Member Projects
DimeCasts.Net - Derik Whittaker

Friends of Devlicio.us
Red-Gate Tools For SQL and .NET

NDepend

SlickEdit
 
SmartInspect .NET Logging
NGEDIT: ViEmu and Codekana
LiteAccounting.Com
DevExpress
Fixx
NHibernate Profiler
Unfuddle
Balsamiq Mockups
Scrumy
JetBrains - ReSharper
Umbraco
NServiceBus
RavenDb
Web Sequence Diagrams
Ducksboard<-- NEW Friend!

 



Site Copyright © 2007 CodeBetter.Com
Content Copyright Individual Bloggers

 

Community Server (Commercial Edition)