| Casual Articles |
Hubs | Hubbers | Topics | Request |
| #1 in Business | Subscribe Email Print |
|
You are here: Home > Business > Management > Must Project Managers Be Technically Savvy? |
|
Casual Articles - Must Project Managers Be Technically Savvy?
Review Of Making Your Richer - Leaves DJK Etc. In The Dust skNB:This is not a sales pitch but merely my review on a website I would highly recommend if you want your financial independence.IntroductionYou may think(and actually convinced yourself) that the e-book you have previously purchased on the internet will let you earn a good second income, enable you to work from home, allow you to quit your day job and tap into internet wealth.But if you think for one minute you bought that e-book for any of those reasons (or ones like them), you're fooling yourself! You bought it because Imagine the following scenario. Your product is scheduled to be released in 5 days. The QA team discovers a defect in the API through a series of CLI tests. After carefully examining the problem, you realize that you're developers have been working around this defect for months. Given that you're only 5 days away from releasing your product, should you fix this defect or document the workaround? At this point in time, how risky is it to modify an API that's being used? How con What Most Employers Don't Want You to Know When They Talk Salary “Must Project Managers be technically savvy?” This topic always seems to cause quite a stir. While some believe that all you need to manage a project is a PMP certification, others are convinced that you can't successfully manage a software development project unless you truly understand the intricacies of the product.When hiring managers describe a salary and benefits package to you, they have one main objective in mind: To get the best possible talent for the least possible expense. They're not going to volunteer the fact that they can go higher in salary or negotiate concessions in your benefits package. So, if you're in the midst of a job change and salary negotiation, here are some important things to keep in mind: Know How Much You're Worth: Well-managed companies conduct regular labor market assessments to determine if their salaries are comp I agree! To be an effective Project Manager, you must know the ins and outs of your solution. You must be capable of designing and developing the solution yourself. Here are 5 fundamental project management tasks that Project Managers can't accomplish unless they have a strong technical background and truly understand the particulars of their product. Estimating Effort In order to create a project plan, you must be able to estimate how much effort is required to complete all of the required tasks. Needless to say, you can't estimate effort unless you truly understand what's involved in designing and implementing those features. Unless you understand what's required to reach 5-9 reliability, you can't assess how much effort is required to achieve this non-functional requirement. Unless you clearly understand how to write Java Server Pages, you can't predict how much development effort is required to transform an HTML prototype to set of fully functional JSP pages. Scheduling Tasks Imagine that someone hands you a list of activities that need to be completed for a given project, along with the overall effort. Could you schedule the tasks in a logical sequence? Should the developers start with the presentation, the business, or the data storage layer? Which comes first when working on a presentation layer: the HTML, the JavaScript, the CSS, or the servlets? A Project Manager must be able to schedule activities in a logical sequence. If you can't determine which activities must come first and which ones can be done in parallel, you can't put together a project schedule. Assessing Risk Imagine the following scenario. Your product is scheduled to be released in 5 days. The QA team discovers a defect in the API through a series of CLI tests. After carefully examining the problem, you realize that you're developers have been working around this defect for months. Given that you're only 5 days away from releasing your product, should you fix this defect or document the workaround? At this point in time, how risky is it to modify an API that's being used? How conf Take the Extra Step, Enjoy the Extra Business e 5 fundamental project management tasks that Project Managers can't accomplish unless they have a strong technical background and truly understand the particulars of their product.Heather and Mark work at a leading attorneys’ office in Seattle. They order fresh ground coffee for the office every month, and sent me this comparison between two major coffee vendors.Coffee company ‘Torrefazione’ (I name the winners)• We received a call from a customer service representative about a coffee order placed at their website earlier in the week.• We were informed that shipments are sent by UPS, but their coffee warehouse is only a few blocks from our office. So they offered to send future orders via courier Estimating Effort In order to create a project plan, you must be able to estimate how much effort is required to complete all of the required tasks. Needless to say, you can't estimate effort unless you truly understand what's involved in designing and implementing those features. Unless you understand what's required to reach 5-9 reliability, you can't assess how much effort is required to achieve this non-functional requirement. Unless you clearly understand how to write Java Server Pages, you can't predict how much development effort is required to transform an HTML prototype to set of fully functional JSP pages. Scheduling Tasks Imagine that someone hands you a list of activities that need to be completed for a given project, along with the overall effort. Could you schedule the tasks in a logical sequence? Should the developers start with the presentation, the business, or the data storage layer? Which comes first when working on a presentation layer: the HTML, the JavaScript, the CSS, or the servlets? A Project Manager must be able to schedule activities in a logical sequence. If you can't determine which activities must come first and which ones can be done in parallel, you can't put together a project schedule. Assessing Risk Imagine the following scenario. Your product is scheduled to be released in 5 days. The QA team discovers a defect in the API through a series of CLI tests. After carefully examining the problem, you realize that you're developers have been working around this defect for months. Given that you're only 5 days away from releasing your product, should you fix this defect or document the workaround? At this point in time, how risky is it to modify an API that's being used? How con What Is An Employee Timesheet? you understand what's required to reach 5-9 reliability, you can't assess how much effort is required to achieve this non-functional requirement. Unless you clearly understand how to write Java Server Pages, you can't predict how much development effort is required to transform an HTML prototype to set of fully functional JSP pages.Managing employee working hours record in a sheet is what timesheet is all about. Wiki says "A timesheet is a method for recording the amount of a worker's time spent on each job". Another way of looking at it is a document or entry program used to record actual labor time against an order or project, that may also specify the operation, location and category or type of task being performed is a Timesheet.A timesheet is a record of time spent on a job by an employee originally for the employer to determine the payroll. They are an Scheduling Tasks Imagine that someone hands you a list of activities that need to be completed for a given project, along with the overall effort. Could you schedule the tasks in a logical sequence? Should the developers start with the presentation, the business, or the data storage layer? Which comes first when working on a presentation layer: the HTML, the JavaScript, the CSS, or the servlets? A Project Manager must be able to schedule activities in a logical sequence. If you can't determine which activities must come first and which ones can be done in parallel, you can't put together a project schedule. Assessing Risk Imagine the following scenario. Your product is scheduled to be released in 5 days. The QA team discovers a defect in the API through a series of CLI tests. After carefully examining the problem, you realize that you're developers have been working around this defect for months. Given that you're only 5 days away from releasing your product, should you fix this defect or document the workaround? At this point in time, how risky is it to modify an API that's being used? How con Franchisors, Lawyers and State Regulators fort. Could you schedule the tasks in a logical sequence? Should the developers start with the presentation, the business, or the data storage layer? Which comes first when working on a presentation layer: the HTML, the JavaScript, the CSS, or the servlets?Most people think that lawyers are crooks and some people think that franchising companies or franchisors are out to make a killing on poor unsuspecting franchisees. State regulators think that Franchisors are not good and lawyers are wonderful. But why? Well because they are lawyers of course. Yet in reality lets look at the situation here.You see, Franchisors duties and responsibilites are to their team, their franchisees customers, extending brand. If the franchisor neglects such duties and responsibilities then they are short live A Project Manager must be able to schedule activities in a logical sequence. If you can't determine which activities must come first and which ones can be done in parallel, you can't put together a project schedule. Assessing Risk Imagine the following scenario. Your product is scheduled to be released in 5 days. The QA team discovers a defect in the API through a series of CLI tests. After carefully examining the problem, you realize that you're developers have been working around this defect for months. Given that you're only 5 days away from releasing your product, should you fix this defect or document the workaround? At this point in time, how risky is it to modify an API that's being used? How con Common Business Myth-You Have To Be A Born Salesperson skWe were all born salespeople. Over the years we have been brainwashed by our family members, our friends and other uninformed people on how NOT to sell, or at least not to sell naturally.Some of the best salespeople don't think of themselves as salespeople. They think of themselves as people that "enjoy" other people.Do you know how to ask questions? Do you know how to listen? Do you know how to carry on a conversation?These are all natural sales skills that we all possess. These are also skills that can be improved dram Imagine the following scenario. Your product is scheduled to be released in 5 days. The QA team discovers a defect in the API through a series of CLI tests. After carefully examining the problem, you realize that you're developers have been working around this defect for months. Given that you're only 5 days away from releasing your product, should you fix this defect or document the workaround? At this point in time, how risky is it to modify an API that's being used? How confident are you that the developer can fix this API in the given timeframe? What's the likelihood that changing this API will break the modules calling it? Should you fix the defect now, or release the product and address the bug in a patch release? Unless you've seen the code behind this interface, you can't answer any of these questions yourself. You need to ask your developers. You're not the decision maker. They are. Participating In Customer Meetings Customer meetings always end up in technical discussions. Unfortunately, if you can't speak intelligently about your technology, you can't add any value to such meetings. You're not participating; you're strictly listening, and perhaps taking notes. Sooner or later, your customers will find themselves contacting your developers directly. “Why contact the Project Manager if he can't give me an answer? I may as well go straight to the source.” Ensuring Nothing Falls Through The Cracks Let's face it. You never get as much time as you'd like to plan your projects. What's important is not that you get it perfect the first time around. What's important is that you can catch the tasks that fell through the cracks before it's too late. If you don't know what's required to complete your solution, you won't be able to identify all the overlooked activities. They'll either be pointed out by your developers, or simply omitted forever. In Short… To be an effective Project Manager, you must be capable of designing and developing the solution yourself. Otherwise, you have two options. You can either (a) ask others to make decisions for you, or (b) simply pretend you know what you're talking about. In the first case, you're a Project Coordinator. In the second case, you're a Project Mangler.
HTTP = HTML link (for blogs, profiles,phorums):
Related Articles:What B-School Did Not Teach: Starting a Business with Two Babies at Home Sun Zi Art of War - Managing a Large Force Like a Small Force Training / Presenting: Stronger Managers and Competent Trainers
|