Liveblogging
Nicole Engard, Jenkins Law Library
problem using email for project planning; difficult to follow and go back to decisions a year later.
Use a blog for each project; give every staff member the ability to contribute to or create a blog. Discussion is still date-stamped.
Everyone can read what is happening in other departments.
Reduces clutter in in-box. Easy to go back to see the year, and complete reports.
Uses wikis for collecting documentation.
She opened up their site live to us and demonstrated some of the features. Kind of hard to transcribe everything, but here are a few things:
They have a shared calendar that is web-based. Everyone is able to edit it.
To do lists - share to do items with other staff, mark items off, keep track of everything. She hasn't said what platform they are using (or perhaps I missed it).
Every staff member has the ability to start their own project.
Staff members don't have to focus on making things look good; they have the power but should focus on writing (i.e. creating content). The web team go in to make things pretty. Web team also have the ability to delete posts, but doesn't happen very often.
Staff get email alerts when things are updated if they want.
Use good web design, icons to make things clear, Dilbert cartoon to inspire people to visit the site. :-)
They have a "future wish list" thread for everyone. Also works for posting meeting minutes and people can post their comments about the meeting.
WYSIWYG editor - WYSIWYG Pro; they also have ability to edit by HTML. They decided to go with editor since it allows for multiple editors on one page. Approx. $40 for non-profits.
Limit the number of Word documents; prefer to term them into wiki pages so they are searchable, easier to handle.
People can read about projects in other departments; improves communication, lets people know what is happening across the organization.
It is an in-house developed platform based on MySQL using PHP for the front end. They would have to do a lot of work to make it available as open source. She is willing to share parts of their code.
See her website where she will post her presentation:
web2learning.net
Showing posts with label project planning. Show all posts
Showing posts with label project planning. Show all posts
Tuesday, April 17, 2007
Accelerated Planning
Selected notes:
Rebecca Jones, Dysart & Jones Associates
Project planning elements:
• Clarity
• Preparation – the power of 2:
o 2 minutes to respond to a question
o 2 hours for a meeting
o 2 months to start a new service initiative
o 2 years to get a new project completed
• Competence
• Balance
• Follow through – has to be built right into the plan
Eat complexity one bite at a time – eat the elephant one bite at a time
Identify stakeholders; think of them as individual people, not by their position or as a group. They can make or break your project, and are not the same as your clients.
Environmental scan – becomes a goal within the plan. Get together what we’ve got
see if there are any gaps or holes and SWOT analysis – strengths, weaknesses, opportunities.
**Drafting the document as you go along. As soon as people see things in print it helps get their ideas together. Get your draft out ASAP to refine our thoughts. Feedback/push-back is essential and tells you where you need to focus your attention. No more than 3 to 5 goals; any more then you cannot remember them.
Core team – accelerating the process
• Everybody plays by the same rules
• No hidden agendas
• If you are off-setting stress with humour, make sure it is funny to everyone
By writing out the draft document, it starts to give a vision – position for discussion throughout the organization. You start to have a conversation around the strategy. If we do this and not something else, what are the consequences? Can we live with the consequences?
Balance:
Dealing with reality – figure out first what you want to happen. Figure out what barriers will stand in your way so you can deal with them. Pay attention to what barriers you are going to influence and deal with them. Then figure out critical success factors. Focus on steps that are critical. Relationships are key- you all have to work together.
Follow-through:
In one day (one long day) – close the library and bring all people together
Prior to the meeting:
• Have draft SWOT
• Have draft mission
At the meeting:
• Have a stakeholder help set the tone of the meeting; or a highly respected person from outside the organization, explaining the importance to show the alignment of what you are doing
• Review SWOT & environmental scan
• You want to create a draft vision for the future
• Draft segmented market, offerings, capabilities & strategies
• Identify what the next steps are – emailed to them
After the meeting
• Documentation
• Development tactics
You will not please everyone. Acknowledge you will not know everything to make the decisions.
Rebecca Jones, Dysart & Jones Associates
Project planning elements:
• Clarity
• Preparation – the power of 2:
o 2 minutes to respond to a question
o 2 hours for a meeting
o 2 months to start a new service initiative
o 2 years to get a new project completed
• Competence
• Balance
• Follow through – has to be built right into the plan
Eat complexity one bite at a time – eat the elephant one bite at a time
Identify stakeholders; think of them as individual people, not by their position or as a group. They can make or break your project, and are not the same as your clients.
Environmental scan – becomes a goal within the plan. Get together what we’ve got
see if there are any gaps or holes and SWOT analysis – strengths, weaknesses, opportunities.
**Drafting the document as you go along. As soon as people see things in print it helps get their ideas together. Get your draft out ASAP to refine our thoughts. Feedback/push-back is essential and tells you where you need to focus your attention. No more than 3 to 5 goals; any more then you cannot remember them.
Core team – accelerating the process
• Everybody plays by the same rules
• No hidden agendas
• If you are off-setting stress with humour, make sure it is funny to everyone
By writing out the draft document, it starts to give a vision – position for discussion throughout the organization. You start to have a conversation around the strategy. If we do this and not something else, what are the consequences? Can we live with the consequences?
Balance:
Dealing with reality – figure out first what you want to happen. Figure out what barriers will stand in your way so you can deal with them. Pay attention to what barriers you are going to influence and deal with them. Then figure out critical success factors. Focus on steps that are critical. Relationships are key- you all have to work together.
Follow-through:
In one day (one long day) – close the library and bring all people together
Prior to the meeting:
• Have draft SWOT
• Have draft mission
At the meeting:
• Have a stakeholder help set the tone of the meeting; or a highly respected person from outside the organization, explaining the importance to show the alignment of what you are doing
• Review SWOT & environmental scan
• You want to create a draft vision for the future
• Draft segmented market, offerings, capabilities & strategies
• Identify what the next steps are – emailed to them
After the meeting
• Documentation
• Development tactics
You will not please everyone. Acknowledge you will not know everything to make the decisions.
Subscribe to:
Posts (Atom)