Any Recommendations for Project Management Software?


One issue I have always had with most software project tool is load balancing between planning and implementing stages. The issue we need to plan the type of skill level with load balancing to project expected levels and types staffing per roles needed. Said another way, we use staffing by categories to forecast staffing by role needed – so we can consider roles needed in combination with learning level requirements. Consider, the skill level within a defined role of a given person changes very significantly between six, twelve, eighteen, and 24 months but is fairly constant from 2 years to 5 years. Thus, if your resources are limited to people with less than 2 years more training and supervision will be required with the six months level requiring the most. This same grading of level of experience applies equal to company knowledge (acculturation effect) level of experience, another significant forecasting issue that can increase funding levels. And so-on and so-on .
However, when we assign an actual person, they may fill more than one of these forecasted roles and they are usually over loaded (how about 120 for a 40 hour work week). Obviously you can’t avoid this overload skewing. It can be mitigated as long as it does overly skew monthly, quarterly or yearly manhour planning. Once the initial planning with overall WBS has been iterated a couple of times a guesstimate of actually staffing levels can be used, But this doesn’t guarantee the actual persons wanted can be acquired so recasting using a scheme such as PA1, PA2, etc can be used to possibly reduce the eventual skewing of actual person/role versus manhours forecasting. Also, one would like the system to keep this staff forecasting by role for comparison against actual staffing. More fun stuff…

LinkedIn: The Project Manager Network – #1 Group for Project Managers
Topic: Any recommendations for a project management software?

INCREASE YOUR INTERNET-ENABLED DEVICE or LAPTOP SECURITY – New Year Alert!

Gallery


Using your laptop or internet-enabled device to get work done away from your office or on the road is becoming widely accepted………………………………….

Use this list of tips to learn how you can keep your internet-enabled device laptop more secure where ever you are travel – out-of-town or between office (formal or informal) and home.

Traveling or at your coffee barista or at your office or home base, increases your internet-enabled device security exposure. Said another way, reduce your laptop security risk. Rapid growth in laptop computing has made portable systems the target for theft around the world – while traveling, at your informal office / coffee stop, or at home. Also, if your laptop computer is stolen, company information and very personal information is exposed, such as your very private personal and financial information. Continue reading

(SEM+BI)+SOA(SECURITY+)+SEO Framework Issues


Should BI teams be more focused on the business side of things or should they have technical IT expertise?

i4Aid/Internet4Aid RESPONSE:

Ajay Sharma • There is no one answer to this question. BI teams have multiple roles – some of which fit in the business side while others in IT. PMO role is required to manage and deliver to the timelines and comitments from various groups involved in a typical BI project. While business owns the functionality and final outcome of the project, IT should own the infrastrucutre, maintenence, licensing, operational aspects of the BI project. There is general accusation that IT slows down teh project and cant keep pace with the agility required by the business. This is a true statement but can be addressed by carefully designing BI project teams. There are various models that can be implemented based on organization’s structure and culture.

i4Aid • My quick response is that Ajay Sharma presented the appropriate basics including his notion about the integration aspects. Briefly, BI should fill out management policies and provide the first break-down levels for the functional processes but not more than 5 levels of detail. Then IT should review and integrate these processes into their IT framework before doing more levels of detail – it is a kind of first scope and impact estimations as they adjust and balance conceptualization and implementation. Then review and balance with both parties – do this before before specifying any more detail processes and procedures and agree on any high level the risk factors. Then do a rough estimate of project timeline.

We did this on the Toyota Motors, USA National Parts System development and it remained fairly scoped for 1-2 years of our development process such that IBM adopted most of this high-level approach.

I will be entering this in my blog: i4Aid.WordPress.com