Bindings, Platforms, and Innovation
This presentation focuses on the Internet and separating myth from fact, history from the future, and the mundane from the imaginative. Bob Frankston presents a vision of what could and should be.
Tracking change and innovation in the enterprise software development community
Posted by Vikas Hazrati on Apr 11, 2008 12:31 PM
In an interesting thread on Group Facilitation list, Jerome Passmore has started a discussion on how to address and prevent facilitator burnout. Responders generally agreed that burnout is a reality, and that one key is reflection to identify when it is creeping up on you.Is all this leading to overburdening of facilitators? Are they trying to do much more than they can possibly handle?
- Basic Agile Work administrative skills.
- Obstacle removal.
- Team dynamics and development.
- Coaching individuals.
- Organizational development.
- Training groups and teams.
- Promoting agile methods.
- Strategic application of agile methods.
I have learned I need to limit the number of days in a week that I facilitate, especially if there is conflict in the group. I've learned that if I book more than three full days a week, I'm past what my heart and energy want to do.Another strategy was suggested by Jo Nelson
I spent as much time as I could carve out alone, where I didn't have to interact with anyone. For me, the natural world is re-energizing, so I found places and times I could go for long, slow, wondering walks alone. I read upbeat fiction, and did creative hand craft work that demanded no intellectual or verbal energy. I did lots of yoga and breathing exercises. I listened to the music that centres me.John Powderly seems to have come out with an interesting way to deal with facilitation burnout, he added:
I no longer call myself a facilitator! Facilitation is now a skill and/or a philosophical basis for what I do, and less associated with my identity. Currently, I call myself "a strategic research, planning andGroup members seemed to agree that, with all the primary and secondary tasks associated with facilitation, burnout was a reality. The difference lies in identifying when you are close to that stage and then taking corrective action immediately. Jo's closing remarks suggest that the key is in noticing when the facilitator is getting close to burnout. This is the time to reflect on your core values, and try to evolve a strategy which keeps you energized and sane. The final step is to follow those strategies.
collaboration specialist", but this may still change as I continue to emerge.
Agile Development: A Manager's Roadmap for Success
Give-away eBook – Confessions of an IT Manager
It sounds a bit like being an entrepreneur or a real estate agent. Your customers and clients need you almost around the clock, and if you want to be great, you have to almost be "on" nearly all the time. Of course, entrepreneurs and real estate agents are paid on commission, so there's an incentive there that would be lacking in a facilitator.
Your customers and clients need you almost around the clock, and if you want to be great, you have to almost be "on" nearly all the time.
I think that is the key and in order to be there for the client and the team the facilitators tend to overwork and take on more work than what can be handled easily.
I am not sure whether you would agree or not, in most situations whatever amount of work a facilitator tries to put in towards the end it is a thankless job, something which was implicitly expected from the facilitator.
I detect my burnout approaching when my regular 1-1 team member reviews highlight non-healthy behaviour or negative attitude surfacing on my part. Then its time for a quick break (physical, emotional and mental) from things and reflection, a reminder of the future success I am working for, and/or other "carrot" in the form of a ideal holiday planning session or taking session :)
This presentation focuses on the Internet and separating myth from fact, history from the future, and the mundane from the imaginative. Bob Frankston presents a vision of what could and should be.
This article explores the use of JBoss and jBPM to implement design solutions that effectively address the issue of orchestrating long running activities.
This presentation covers the use of graph databases as an optimal solution for data that is difficult to fit in static tables, rapidly evolving data or data that has a lot of optional attributes.
This session introduces Real Options and shows how it can help in running your project. Real Options is a decision-making process that can be used to manage risk.
This article discusses the use of bindings on services and references (including the instance of non-configured bindings) as the means to implement SCA communications in a Web and SOA environment.
After a short introduction to DSLs, Scott Davis plays with the keyboard showing how to approach the creation of a DSL by typing working snippets of Groovy code that get executed.
IBM Rational and InfoQ present, Scaling Agile with C/ALM, an eBook showing organizations how to become “finely tuned software delivery machines” by enabling team integration and scaling.
Amanda Laucher presents a real life enterprise application written in F#. She shows actual code snippets, explaining design decisions and suggesting how to use some of the F# constructs.
3 comments
Watch Thread Reply