<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>eManagr News &#187; Features</title>
	<atom:link href="http://blog.emanagr.com/tag/features/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.emanagr.com</link>
	<description>Happenings with the premiere automated project manager</description>
	<lastBuildDate>Sat, 03 Jul 2010 14:32:19 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=abc</generator>
		<item>
		<title>Teams:  The Hollywood Model [2]</title>
		<link>http://blog.emanagr.com/2009/05/25/teams-and-the-hollywood-model/</link>
		<comments>http://blog.emanagr.com/2009/05/25/teams-and-the-hollywood-model/#comments</comments>
		<pubDate>Mon, 25 May 2009 16:00:55 +0000</pubDate>
		<dc:creator>John</dc:creator>
				<category><![CDATA[Concepts]]></category>
		<category><![CDATA[Features]]></category>
		<category><![CDATA[Principles]]></category>

		<guid isPermaLink="false">http://blog.emanagr.com/2009/05/25/teams-and-the-hollywood-model/</guid>
		<description><![CDATA[Teams are important to eManagr, so much so that the project&#8217;s codename was &#8220;TeamrUp;&#8221; its job, after all, is to be a &#8220;teamer&#8221; for you. While the scope quickly expanded beyond a typical distributed spreadsheet (I&#8217;m looking at you, Team System), the teams have remained a core priority. What&#8217;s the big deal? Teams fluctuate. Organizational [...]]]></description>
			<content:encoded><![CDATA[<p>Teams are important to eManagr, so much so that the project&#8217;s codename was &#8220;TeamrUp;&#8221; its job, after all, is to be a &#8220;teamer&#8221; for <em>you</em>.  While the scope quickly expanded beyond a typical distributed spreadsheet (I&#8217;m looking at you, <a href="http://msdn.microsoft.com/en-us/teamsystem/default.aspx">Team System</a>), the teams have remained a core priority.</p>
<p>What&#8217;s the big deal?<span id="more-8"></span></p>
<p>Teams fluctuate.  Organizational charts change frequently.  Workload is shouldered through various outsourcing firms.  People come and go.  In other words, your team is very likely fluid, and if we can help you form and organize your team faster and better, then that&#8217;s one distraction we&#8217;re happy won&#8217;t worry you.</p>
<p>The <u>Hollywood model</u> is about precisely this.  Rather than attack a problem in terms of &#8220;resources&#8221; to be used, eManagr thinks in terms of tasks to complete and the people qualified to complete the task.</p>
<p>When a producer creates a movie, she starts with a writer&#8217;s script.  Often, she has directors with whom she enjoys working, and brings one in who has the time.  The roles in the script may also suggest actors these managers have already worked with, and so the cast and crew is built from relationships.  Where there isn&#8217;t a relationship, the producer wants people with the best reputations.</p>
<p>And that&#8217;s all there is to our model.  Relationships come first and foremost&#8211;you already know how to get in contact with your associates on eManagr.  If your circumstances don&#8217;t permit any further recruitment, that&#8217;s it.  If they do, though, you can search for someone with the skill you need and get the people who have the best objective records for getting their projects done reliably.</p>
<p>But that&#8217;s a story for the next post.</p>
<p>Meanwhile, today is Memorial Day in the United States.  Whatever your politics or belief in any particular war, remember that those who give their lives for their respective countries do so with honorable intentions. Take the opportunity to remember their sacrifices and, as importantly, take time to comfort those who have lost loved ones to wars.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.emanagr.com/2009/05/25/teams-and-the-hollywood-model/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Finally, Visual Schedules</title>
		<link>http://blog.emanagr.com/2009/04/20/finally-visual-schedules/</link>
		<comments>http://blog.emanagr.com/2009/04/20/finally-visual-schedules/#comments</comments>
		<pubDate>Mon, 20 Apr 2009 16:00:30 +0000</pubDate>
		<dc:creator>John</dc:creator>
				<category><![CDATA[Development]]></category>
		<category><![CDATA[Features]]></category>
		<category><![CDATA[Updates]]></category>

		<guid isPermaLink="false">http://blog.emanagr.com/2009/04/20/finally-visual-schedules/</guid>
		<description><![CDATA[It&#8217;s not a Gantt chart, but it should be close enough for a lot of people. We knew when we launched that many people wouldn&#8217;t be willing to use eManagr because there was no easy way to get the project&#8217;s status &#8220;at a glance.&#8221; So, as mentioned a few weeks ago, this was a top [...]]]></description>
			<content:encoded><![CDATA[<p>It&#8217;s not a Gantt chart, but it should be close enough for a lot of people.</p>
<p><span id="more-9"></span></p>
<p>We knew when we launched that many people wouldn&#8217;t be willing to use eManagr because there was no easy way to get the project&#8217;s status &#8220;at a glance.&#8221;  So, as mentioned <a href="http://blog.emanagr.com/2009/03/09/coming-attractions/">a few weeks ago</a>, this was a top feature to add.</p>
<p>At the top of every project page, we have added a link to view the schedule.  There, you can see the tasks assigned to each member of the team in priority order, either as a list or as a chart.</p>
<p>The chart should be completely intuitive.  Each task is a box with a color that contrasts strongly against its neighbors.  It&#8217;s width indicates how long the task is likely to take, and a blue horizontal line indicates how close the task is to completion.  You can hover over the task for more information, and click through to the task&#8217;s detail page.</p>
<p>For example, this is what my own workload will look like for eManagr itself over the next few months:</p>
<div id="attachment_26" class="wp-caption aligncenter" style="width: 601px"><img class="size-full wp-image-26" title="Sample Schedule" src="http://blog.emanagr.com/wp-content/uploads/2009/07/schedsample.png" alt="John's work for eManagr" width="591" height="219" /><p class="wp-caption-text">John&#39;s work for eManagr</p></div>
<p>As I said at the top, it&#8217;s not a Gantt chart (though it can be, after we add some related features), but it&#8217;s something that a non-technical manager can look at to see how well the team is doing.  Give it a try, and tell us what you think.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.emanagr.com/2009/04/20/finally-visual-schedules/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Introducing eManagr [1]</title>
		<link>http://blog.emanagr.com/2009/02/23/introducing-emanagr/</link>
		<comments>http://blog.emanagr.com/2009/02/23/introducing-emanagr/#comments</comments>
		<pubDate>Mon, 23 Feb 2009 17:00:54 +0000</pubDate>
		<dc:creator>John</dc:creator>
				<category><![CDATA[Overview]]></category>
		<category><![CDATA[Features]]></category>
		<category><![CDATA[Principles]]></category>
		<category><![CDATA[Updates]]></category>

		<guid isPermaLink="false">http://blog.emanagr.com/2009/02/23/introducing-emanagr/</guid>
		<description><![CDATA[Yes. Usually. Not really. That should explain everything. You want the actual questions? Picky. Does the world need another project manager? Does the world need another e-something? Does the world need another quirkily misspelled domain name? When development started on eManagr, I wanted something special. I wanted a system that would work for us rather [...]]]></description>
			<content:encoded><![CDATA[<p>Yes.  Usually.  Not really.</p>
<p>That should explain everything.  You want the actual questions?  Picky.</p>
<p>Does the world need another project manager?  Does the world need another e-something?  Does the world need another quirkily misspelled domain name?<br />
<span id="more-3"></span></p>
<p>When development started on eManagr, I wanted something special.  I wanted a system that would work for us rather than become another burden.  In other words, eManagr need to actually <em>manage</em> your team, so that your team can, you know, get to work.   It also needs to be a <em>good</em> manager and stay out of your way when you&#8217;re working.  I&#8217;m measuring success only on how well it does that, not how many Microsoft Office features got crammed in.</p>
<p><tt></tt>First things first, eManagr doesn&#8217;t waste your time with customization.  It looks like a legal pad.  Verification takes more time than production.   Tasks are more important if they&#8217;re shorter and more popular.  Live with it, because the hours you spend arguing about how, exactly, to determine importance is a complete waste of time.  eManagr might not know better than you, but like the best managers, a good enough decision isn&#8217;t up for debate until the real work is done.</p>
<p>Second, eManagr tracks your work.  Partly, this is to help you eliminate time-sheets (an upcoming feature).  But more importantly, it helps you give a better estimate for future work.  Most stakeholders don&#8217;t care <em>when</em> something gets done.  They really care that you get it done when you said you would, so they can plan around it.</p>
<p>Third, eManagr communicates by e-mail.  You know, every time management guru tells you to stop checking your inbox.  And you know what?   Nobody&#8217;s stopping.  So as long as you have the bad habit, we make it work <em>for</em> you.  Once you create your account, you don&#8217;t need to go back to the website for every little thing.  Fire off a message, even from your phone on the road, and eManagr will update things for you.</p>
<p>Fourth, we think a project runs smoothest when everybody has a say.  Therefore, our priority system is semi-democratic.  Everybody on the team can vote on project features, and eManagr will schedule those with the most votes first.  However, since dictators can get things done quickly, managers can allow some voters to be &#8220;more equal than others.&#8221;</p>
<p>Lastly, we don&#8217;t know you.  You might be the CEO of a multinational corporation.  You might be an employee of a start-up.  You might participate in Open Source projects.  You might be an artist.  You might even be a student working on a group project.  Because of that variety, our teams use the &#8220;Hollywood&#8221; model.  At any time, you can start a new team and staff it with any other eManagr users.  You can ask subordinates, coworkers, friends, family, or consultants to join your team, and immediately assign work to them.</p>
<p>In other words, eManagr directs you and makes suggestions, but above all else, lets you do your job.  And that is exactly what I wanted to see.</p>
<p>Is there more work to do?  Sure.  We have a whole bunch of features that we&#8217;ll be rolling out in the coming months.  It&#8217;s exciting.  But it&#8217;s also too much material for this post, which is already too long by half.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.emanagr.com/2009/02/23/introducing-emanagr/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
