<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' xmlns:georss='http://www.georss.org/georss' xmlns:gd='http://schemas.google.com/g/2005' xmlns:thr='http://purl.org/syndication/thread/1.0'><id>tag:blogger.com,1999:blog-9542980</id><updated>2012-02-01T01:42:17.352-08:00</updated><title type='text'>Brave New World of Project Management</title><subtitle type='html'>Addresses common sense project management--how to make it work for real people with real constraints in a real world seeking real results.  </subtitle><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://bnwofpm.blogspot.com/feeds/posts/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9542980/posts/default?max-results=100'/><link rel='alternate' type='text/html' href='http://bnwofpm.blogspot.com/'/><link rel='hub' href='http://pubsubhubbub.appspot.com/'/><author><name>Krista G.</name><uri>http://www.blogger.com/profile/00056855826917590007</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>20</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>100</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-9542980.post-112649532751036056</id><published>2005-10-13T19:24:00.000-07:00</published><updated>2005-10-19T08:03:31.080-07:00</updated><title type='text'>A Philosophy of Whole Systems</title><summary type='text'>I don't usually quote Pythagoras in my daily work, but in my 'off-hours' reading I was given an article by a friend that surveyed Pythagoras' theories (beyond the well-known theorem) In thinking about the concepts, I found it really had implications for Program Management as well.Why should you care? The fundamental concepts of Pythagoras deal with the harmony between self and the other through </summary><link rel='replies' type='application/atom+xml' href='http://bnwofpm.blogspot.com/feeds/112649532751036056/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=9542980&amp;postID=112649532751036056' title='4 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9542980/posts/default/112649532751036056'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9542980/posts/default/112649532751036056'/><link rel='alternate' type='text/html' href='http://bnwofpm.blogspot.com/2005/10/philosophy-of-whole-systems.html' title='A Philosophy of Whole Systems'/><author><name>Krista G.</name><uri>http://www.blogger.com/profile/00056855826917590007</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>4</thr:total></entry><entry><id>tag:blogger.com,1999:blog-9542980.post-112104472040186200</id><published>2005-07-27T17:54:00.000-07:00</published><updated>2005-07-27T20:48:02.690-07:00</updated><title type='text'>Recipe for Project Management Hell</title><summary type='text'> Real life has inspired postulation again...Ingredients:2 c. strong personalities1 c. complex technical configuration1 c.  complex business need1 c. ambitious project1/2 c. manager bonus depends on project1/2 c.  negative past experiences1/2 c.  lack of trust1/4 c.  bad attitudeSaute the first three ingredients until translucent.  Stir in the ambitious project and political pressure of management</summary><link rel='replies' type='application/atom+xml' href='http://bnwofpm.blogspot.com/feeds/112104472040186200/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=9542980&amp;postID=112104472040186200' title='4 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9542980/posts/default/112104472040186200'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9542980/posts/default/112104472040186200'/><link rel='alternate' type='text/html' href='http://bnwofpm.blogspot.com/2005/07/recipe-for-project-management-hell.html' title='Recipe for Project Management Hell'/><author><name>Krista G.</name><uri>http://www.blogger.com/profile/00056855826917590007</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>4</thr:total></entry><entry><id>tag:blogger.com,1999:blog-9542980.post-112166342505941260</id><published>2005-07-17T21:54:00.000-07:00</published><updated>2005-08-11T21:52:15.876-07:00</updated><title type='text'>Lessons learned: Ants</title><summary type='text'>While out on a walk struggling with the utter lack of cooperation of my team lately (okay that's the desperation talking), I observed a trail of ants diligently going about their task. No, fervently going about their task. I thought, "What is it about ant society makes it work so well?" Admittedly, I discovered them because I put my hand smack dab in the middle of their thoroughfare and they were</summary><link rel='related' href='http://en.wikipedia.org/wiki/Ants' title='Lessons learned: Ants'/><link rel='replies' type='application/atom+xml' href='http://bnwofpm.blogspot.com/feeds/112166342505941260/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=9542980&amp;postID=112166342505941260' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9542980/posts/default/112166342505941260'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9542980/posts/default/112166342505941260'/><link rel='alternate' type='text/html' href='http://bnwofpm.blogspot.com/2005/07/lessons-learned-ants.html' title='Lessons learned: Ants'/><author><name>Krista G.</name><uri>http://www.blogger.com/profile/00056855826917590007</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-9542980.post-112023222097709501</id><published>2005-07-01T08:22:00.000-07:00</published><updated>2005-07-01T08:37:00.983-07:00</updated><title type='text'>Effective Uses of Flowcharts</title><summary type='text'>From The Vision Thing:"A flowchart is not a 1:1 substitute for clearly written procedures. As in the case of the above examples, flowcharts are excellent tools to check the logic of a given process, or to sketch out a given concept prior to drafting more formal instructions."This is particularly interesting to me right now since I am attempting to create a flowchart-centric process site on our </summary><link rel='related' href='http://www.thevisionthing.com/index.php?p=621' title='Effective Uses of Flowcharts'/><link rel='replies' type='application/atom+xml' href='http://bnwofpm.blogspot.com/feeds/112023222097709501/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=9542980&amp;postID=112023222097709501' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9542980/posts/default/112023222097709501'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9542980/posts/default/112023222097709501'/><link rel='alternate' type='text/html' href='http://bnwofpm.blogspot.com/2005/07/effective-uses-of-flowcharts.html' title='Effective Uses of Flowcharts'/><author><name>Krista G.</name><uri>http://www.blogger.com/profile/00056855826917590007</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-9542980.post-111867915850171300</id><published>2005-06-13T09:03:00.000-07:00</published><updated>2005-06-13T09:12:45.623-07:00</updated><title type='text'>Excuses not accepted</title><summary type='text'>Another post sparked a thought for something that needs to be worked into the PMO development...a list of excuses that we as a team do not accept. On Project, Process, and Business Improvement...AJ put up a list he most commonly hears:"Table of ExcusesI wanted to note the top-ten excuses I run into when following up on tasks, but lengthened the list to twelve. So here it goes:12. I wasn't hired </summary><link rel='replies' type='application/atom+xml' href='http://bnwofpm.blogspot.com/feeds/111867915850171300/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=9542980&amp;postID=111867915850171300' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9542980/posts/default/111867915850171300'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9542980/posts/default/111867915850171300'/><link rel='alternate' type='text/html' href='http://bnwofpm.blogspot.com/2005/06/excuses-not-accepted.html' title='Excuses not accepted'/><author><name>Krista G.</name><uri>http://www.blogger.com/profile/00056855826917590007</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-9542980.post-111867697663216640</id><published>2005-06-13T08:31:00.000-07:00</published><updated>2005-06-13T08:36:16.640-07:00</updated><title type='text'>Tom Peters rules of teamship</title><summary type='text'>Got something useful from Tom Peters blog today (I know!).... Below are his UK company's rules for teamship.  I found 3 and 5 especially poignant right now... probably because I am struggling with accountability and how to reinforce it through the systems we create rather than just some silly lip service.  I wonder if I gave the workgroup the opportunity to create their own rules of teamwork if </summary><link rel='replies' type='application/atom+xml' href='http://bnwofpm.blogspot.com/feeds/111867697663216640/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=9542980&amp;postID=111867697663216640' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9542980/posts/default/111867697663216640'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9542980/posts/default/111867697663216640'/><link rel='alternate' type='text/html' href='http://bnwofpm.blogspot.com/2005/06/tom-peters-rules-of-teamship.html' title='Tom Peters rules of teamship'/><author><name>Krista G.</name><uri>http://www.blogger.com/profile/00056855826917590007</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-9542980.post-111818427220637328</id><published>2005-06-07T15:43:00.000-07:00</published><updated>2005-06-07T15:44:32.213-07:00</updated><title type='text'>Affect of Culture on communication/knowledge management</title><summary type='text'>From Knowledge Jolt with Jack (6/2/05)--Here are the four ways in which culture influences knowledge, from the perspective of this article:Culture influences the definition of knowledge and what is worth saving.I particularly like this idea.  Each company, or sub-unit have their view of the world and internal values that influence how they treat knowledge and what they believe is important.  </summary><link rel='replies' type='application/atom+xml' href='http://bnwofpm.blogspot.com/feeds/111818427220637328/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=9542980&amp;postID=111818427220637328' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9542980/posts/default/111818427220637328'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9542980/posts/default/111818427220637328'/><link rel='alternate' type='text/html' href='http://bnwofpm.blogspot.com/2005/06/affect-of-culture-on.html' title='Affect of Culture on communication/knowledge management'/><author><name>Krista G.</name><uri>http://www.blogger.com/profile/00056855826917590007</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-9542980.post-111816077310692640</id><published>2005-06-07T08:41:00.000-07:00</published><updated>2005-06-07T09:12:53.110-07:00</updated><title type='text'>Topics for MAPP Training</title><summary type='text'>The more I think about the MAPP rollout, the more I realize we need to have a series of topics covered.  Rather than focus on the text book version of project management, I want people to recognize the set of skills necessary to achieve success on projects. I identified two components that should be included. Leadership - I read a quote in PM Network that project managers are really change </summary><link rel='replies' type='application/atom+xml' href='http://bnwofpm.blogspot.com/feeds/111816077310692640/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=9542980&amp;postID=111816077310692640' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9542980/posts/default/111816077310692640'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9542980/posts/default/111816077310692640'/><link rel='alternate' type='text/html' href='http://bnwofpm.blogspot.com/2005/06/topics-for-mapp-training.html' title='Topics for MAPP Training'/><author><name>Krista G.</name><uri>http://www.blogger.com/profile/00056855826917590007</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-9542980.post-111815891051687072</id><published>2005-06-07T08:35:00.000-07:00</published><updated>2005-06-07T08:41:50.520-07:00</updated><title type='text'>Quarterly Project Showcase</title><summary type='text'>Reading in PM Network and they had an idea for a basic seminar type event where the PMO could coordinate a report out on projects at their conclusion.  It is to help spread best practices, common practices throughout the organization.  This allows people to not have to reinvent the wheel everytime. Although I would structure it slightly differently, I think this could be a good process for MAPP </summary><link rel='replies' type='application/atom+xml' href='http://bnwofpm.blogspot.com/feeds/111815891051687072/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=9542980&amp;postID=111815891051687072' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9542980/posts/default/111815891051687072'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9542980/posts/default/111815891051687072'/><link rel='alternate' type='text/html' href='http://bnwofpm.blogspot.com/2005/06/quarterly-project-showcase.html' title='Quarterly Project Showcase'/><author><name>Krista G.</name><uri>http://www.blogger.com/profile/00056855826917590007</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-9542980.post-111774043225399191</id><published>2005-06-02T12:24:00.000-07:00</published><updated>2005-06-02T12:27:32.806-07:00</updated><title type='text'>Motivation and Trust</title><summary type='text'>Saw an interesting post on Motivation... something that is incredibly important to any initiative I undertake... that and buyin...Motivation consists of three elements:Expectations about abilityExpectations about resultsPreferencesWhen we're deciding whether to do an action, we evaluate all three of these elements, often intuitively or unconsciously. The end result—our motivation for or against </summary><link rel='replies' type='application/atom+xml' href='http://bnwofpm.blogspot.com/feeds/111774043225399191/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=9542980&amp;postID=111774043225399191' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9542980/posts/default/111774043225399191'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9542980/posts/default/111774043225399191'/><link rel='alternate' type='text/html' href='http://bnwofpm.blogspot.com/2005/06/motivation-and-trust.html' title='Motivation and Trust'/><author><name>Krista G.</name><uri>http://www.blogger.com/profile/00056855826917590007</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-9542980.post-110575081953958992</id><published>2005-01-14T16:59:00.000-08:00</published><updated>2005-01-14T17:25:08.256-08:00</updated><title type='text'>“You can’t drop a ball that isn’t in your court.”</title><summary type='text'>It can be used for good or it can be used for evil. No, I’m not talking about lawnmowers or even COM’s single threaded apartments. Its the occasional habit of experienced project managers to quickly return requests to their clients for “clarification". A project manager once described it using a dangerously mixed metaphor:“You can’t drop a ball that isn’t in your court.”If this practice is </summary><link rel='related' href='http://www.nerdherding.net/2005/01/12/you-cant-drop-a-ball-that-isnt-in-your-court/' title='“You can’t drop a ball that isn’t in your court.”'/><link rel='replies' type='application/atom+xml' href='http://bnwofpm.blogspot.com/feeds/110575081953958992/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=9542980&amp;postID=110575081953958992' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9542980/posts/default/110575081953958992'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9542980/posts/default/110575081953958992'/><link rel='alternate' type='text/html' href='http://bnwofpm.blogspot.com/2005/01/you-cant-drop-ball-that-isnt-in-your.html' title='“You can’t drop a ball that isn’t in your court.”'/><author><name>Krista G.</name><uri>http://www.blogger.com/profile/00056855826917590007</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-9542980.post-110538295517625910</id><published>2005-01-10T10:47:00.000-08:00</published><updated>2005-01-11T08:45:27.410-08:00</updated><title type='text'>Costing Meeting Inefficiency</title><summary type='text'>No more wasting time and $$ in meetings!  For a small amount of discipline in managing meetings there are pretty big intangible rewards.Through creating regular agendas and meeting notes, the meeting planner creates a number of side benefits:1) Trust - helping you now will be reciprocated later, you are using my time efficiently, and valuing my opinion.2) Broadened perspective - assuring that</summary><link rel='related' href='http://valuemanagementpartners.com/blog/index.rdf' title='Costing Meeting Inefficiency'/><link rel='replies' type='application/atom+xml' href='http://bnwofpm.blogspot.com/feeds/110538295517625910/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=9542980&amp;postID=110538295517625910' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9542980/posts/default/110538295517625910'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9542980/posts/default/110538295517625910'/><link rel='alternate' type='text/html' href='http://bnwofpm.blogspot.com/2005/01/costing-meeting-inefficiency.html' title='Costing Meeting Inefficiency'/><author><name>Krista G.</name><uri>http://www.blogger.com/profile/00056855826917590007</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-9542980.post-110538272193817523</id><published>2005-01-10T10:44:00.000-08:00</published><updated>2005-01-11T08:48:18.530-08:00</updated><title type='text'>What is a project?</title><summary type='text'>(Found this definition...sorry I have lost the original source so I can't give credit where its due. )A project is....It has more than one physical action. Its desired outcome is valuable, desirable, and well articulated (even if it needs to change or adapt as the project's constraints evolve). Everyone involved in the project understands and agrees on the project's value and desirable outcome (</summary><link rel='replies' type='application/atom+xml' href='http://bnwofpm.blogspot.com/feeds/110538272193817523/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=9542980&amp;postID=110538272193817523' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9542980/posts/default/110538272193817523'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9542980/posts/default/110538272193817523'/><link rel='alternate' type='text/html' href='http://bnwofpm.blogspot.com/2005/01/what-is-project.html' title='What is a project?'/><author><name>Krista G.</name><uri>http://www.blogger.com/profile/00056855826917590007</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-9542980.post-110538229278167681</id><published>2005-01-10T10:37:00.000-08:00</published><updated>2005-01-11T08:54:57.723-08:00</updated><title type='text'>Realistic Timelines</title><summary type='text'>Project network as a social network --"We so often think about these branching and interconnected networks as a fancy list of tasks. Built well, they represent interdependencies among people and the tasks. But the insight above really gets at the people nature of projects. There aren't hard cutoffs between the end of one task and the beginning of another. The line on the gantt chart implies a </summary><link rel='related' href='http://jackvinson.com/archives/2004/07/28/project_network_as_a_social_network.html' title='Realistic Timelines'/><link rel='replies' type='application/atom+xml' href='http://bnwofpm.blogspot.com/feeds/110538229278167681/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=9542980&amp;postID=110538229278167681' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9542980/posts/default/110538229278167681'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9542980/posts/default/110538229278167681'/><link rel='alternate' type='text/html' href='http://bnwofpm.blogspot.com/2005/01/realistic-timelines.html' title='Realistic Timelines'/><author><name>Krista G.</name><uri>http://www.blogger.com/profile/00056855826917590007</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-9542980.post-110538217236750358</id><published>2005-01-10T10:31:00.000-08:00</published><updated>2005-03-11T12:40:33.163-08:00</updated><title type='text'>Multi-project Oversight</title><summary type='text'>A great table illustrating multi-project mangement structures The site as a whole is pretty good too! </summary><link rel='replies' type='application/atom+xml' href='http://bnwofpm.blogspot.com/feeds/110538217236750358/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=9542980&amp;postID=110538217236750358' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9542980/posts/default/110538217236750358'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9542980/posts/default/110538217236750358'/><link rel='alternate' type='text/html' href='http://bnwofpm.blogspot.com/2005/01/multi-project-oversight.html' title='Multi-project Oversight'/><author><name>Krista G.</name><uri>http://www.blogger.com/profile/00056855826917590007</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-9542980.post-110537807163395552</id><published>2005-01-10T09:24:00.000-08:00</published><updated>2005-10-13T21:06:14.253-07:00</updated><title type='text'>Accountability and Blame</title><summary type='text'>An issue that will need to be addressed eventually that of Blame vs. Accountability. How do you structure projects so that they maximize project accountability and minimize the opportunity for passing undeserved blame. I believe the first step is to create a culture of support and one where reasonable explanations are heard. Second, once a problem has been voiced, the PM has to be ready to accept</summary><link rel='replies' type='application/atom+xml' href='http://bnwofpm.blogspot.com/feeds/110537807163395552/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=9542980&amp;postID=110537807163395552' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9542980/posts/default/110537807163395552'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9542980/posts/default/110537807163395552'/><link rel='alternate' type='text/html' href='http://bnwofpm.blogspot.com/2005/01/accountability-and-blame.html' title='Accountability and Blame'/><author><name>Krista G.</name><uri>http://www.blogger.com/profile/00056855826917590007</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-9542980.post-110537786624767562</id><published>2005-01-10T09:08:00.000-08:00</published><updated>2005-10-13T21:07:02.940-07:00</updated><title type='text'>Measuring Project Progress</title><summary type='text'>Something I am struggling with as I move forward is how to measure task/project progress. What will most accurately track project information in a way that is satisfactory to execs as well as the project managers?Execs want to know:Is the project going to finish on time?Will there be any tasks that will require more resources or financing than originally anticipated in order to complete on time?</summary><link rel='replies' type='application/atom+xml' href='http://bnwofpm.blogspot.com/feeds/110537786624767562/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=9542980&amp;postID=110537786624767562' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9542980/posts/default/110537786624767562'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9542980/posts/default/110537786624767562'/><link rel='alternate' type='text/html' href='http://bnwofpm.blogspot.com/2005/01/measuring-project-progress.html' title='Measuring Project Progress'/><author><name>Krista G.</name><uri>http://www.blogger.com/profile/00056855826917590007</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-9542980.post-110366062373803660</id><published>2004-12-21T13:23:00.000-08:00</published><updated>2004-12-21T12:55:54.300-08:00</updated><title type='text'>How to Make Meetings Work!</title><summary type='text'> How to Make Meetings Work  is a book I randomly picked up at the UC Berkeley bookstore while a student. I didn't bother reading it of course, because my coursework demanded enough reading each day. However, after taking a new job as a project administrator and discovering the organizational issues surrounding meetings, I thought it might be worth picking up again. And it was...The book </summary><link rel='replies' type='application/atom+xml' href='http://bnwofpm.blogspot.com/feeds/110366062373803660/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=9542980&amp;postID=110366062373803660' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9542980/posts/default/110366062373803660'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9542980/posts/default/110366062373803660'/><link rel='alternate' type='text/html' href='http://bnwofpm.blogspot.com/2004/12/how-to-make-meetings-work.html' title='How to Make Meetings Work!'/><author><name>Krista G.</name><uri>http://www.blogger.com/profile/00056855826917590007</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-9542980.post-110330295093596825</id><published>2004-12-17T09:01:00.000-08:00</published><updated>2004-12-17T13:39:50.680-08:00</updated><title type='text'>Integrated PM based on Theory of Constraints</title><summary type='text'>I went through a demo yesterday for Concerto software that provided a lot of insight. Whether or not we go ahead with their software, I am pretty sure I will integrate some of the ideas inherent in their methodology.It is a software based on the 'Theory of Constraints' and Parkinson's Law-- "Work expands to fill (and often exceed) the time allowed."  Here are the ones I thought were most </summary><link rel='replies' type='application/atom+xml' href='http://bnwofpm.blogspot.com/feeds/110330295093596825/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=9542980&amp;postID=110330295093596825' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9542980/posts/default/110330295093596825'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9542980/posts/default/110330295093596825'/><link rel='alternate' type='text/html' href='http://bnwofpm.blogspot.com/2004/12/integrated-pm-based-on-theory-of.html' title='Integrated PM based on Theory of Constraints'/><author><name>Krista G.</name><uri>http://www.blogger.com/profile/00056855826917590007</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-9542980.post-110269444060929189</id><published>2004-12-10T07:52:00.000-08:00</published><updated>2004-12-10T08:14:58.593-08:00</updated><title type='text'>The Importance of Communication</title><summary type='text'>I have just begun a job as an internal project management consultant for a company. While they have not called it this, I believe I am launching their Program Management Office (PMO) since I will not be responsible for individual projects.  Instead, I will be the brain trust for the projects and how they interrelate between departments. A number of times thoughout the interview process I asked </summary><link rel='replies' type='application/atom+xml' href='http://bnwofpm.blogspot.com/feeds/110269444060929189/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=9542980&amp;postID=110269444060929189' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9542980/posts/default/110269444060929189'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9542980/posts/default/110269444060929189'/><link rel='alternate' type='text/html' href='http://bnwofpm.blogspot.com/2004/12/importance-of-communication.html' title='The Importance of Communication'/><author><name>Krista G.</name><uri>http://www.blogger.com/profile/00056855826917590007</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry></feed>
