A project manager acts as the primary link between business and technical teams. A project manager is responsible for maintaining the project schedule, developing project estimates, working with external teams and tracking project issues. The project manager belongs to either the technical team or the project management office (PMO). The project manager works with business teams, technical teams, business counterparts, testing resources, vendors and infrastructure teams.

A project manager is often challenged with diagonally opposite views from the business side and technical side. A project manager’s success depends on balancing the needs and emotions of both sides.

Understanding the Requirements
A project manager must familiarize with the project’s requirements as defined by the business or product managers. This will help you understand the business vision behind the project. You will need this knowledge while negotiating with the technical teams.

Understanding the Technical Landscape
A project manager must also understand the technical systems, resource skills and infrastructure capabilities available for the project. Business teams come up with expectations that are sometimes beyond the capabilities of the technology team. It is the responsibility of the project manager to understand the technical capabilities available to the project.

Walkthrough of Business Requirements
This is a critical step in the project delivery process. The project manager must invite members from the business team, technical team, testing team, infrastructure team and vendors. The project manager must encourage the various stakeholders to ask questions about the requirements. Any prototypes available must be demonstrated in this meeting. The project manager must find answers to all questions resulting from the requirements walkthrough. The project manager must get the final version of the requirements approved by all stakeholders.

Managing Conflicts in Timelines and Budgets
All project managers will face the conflicts arising from shortened timelines and limited budgets. Business teams typically demand many features that are nearly impossible to deliver within short timeframes. The project manager must work with business and technical teams to prioritize the requirements. If the project is executed in a product development organization, then the project manager could utilize agile methodologies to deliver projects incrementally. In this case, the project manager may be required to act as a scrum master to facilitate scrum meetings between various stakeholders.

The Art of Saying “No”
As a project manager, you may be forced to say “no” to demands from both business and technology teams. However, it is important to create a win-win situation for all parties when you are faced with conflicting demands. You can work with the stakeholders individually before bringing all parties together. Most stakeholders prefer to work together. The success of a project manager depends on how effectively he or she can bring out the best in everyone, driving everyone towards a common goal.

Finally, the job of a project manager is not to satisfy the demands from all corners. The project manager must identify the essential deliverables that will meet the business needs, with a solid understanding of what is possible within the limits of technology.

Related:

Smart Project Management: Best Practices of Good Managers

Is Agism an Issue in IT?

Unless you have a great product, service or idea for which people are willing to wait, chances are highly likely that these potential clients will leave your website should your response time take too long to their incoming requests.  Ignore your application’s performance and you are more likely to be dumped by your users sooner than expected.

To improve the performance of an ASP.Net application you need to optimize your front-end UI (user interface) code as well as the back-end database. You can also think of the following tips as a brief best practices guide for the ASP.net performance optimization. So, whether you are a developer, UI designer or member of the deployment team, the following tips may help you. No matter what’s your role in the project or what you do to boost performance of your application, always remember that your goal should be to:

·          Minimize the amount of data you sent across the network.

·          Reduce the number of server requests.

Here you go (in no particular order)

At Database level

I will begin our blog on Java Tutorial with an incredibly important aspect of java development:  memory management.  The importance of this topic should not be minimized as an application's performance and footprint size are at stake.

From the outset, the Java Virtual Machine (JVM) manages memory via a mechanism known as Garbage Collection (GC).  The Garbage collector

• Manages the heap memory.   All obects are stored on the heap; therefore, all objects are managed.  The keyword, new, allocates the requisite memory to instantiate an object and places the newly allocated memory on the heap.  This object is marked as live until it is no longer being reference.
• Deallocates or reclaims those objects that are no longer being referened. 
• Traditionally, employs a Mark and Sweep algorithm.  In the mark phase, the collector identifies which objects are still alive.  The sweep phase identifies objects that are no longer alive.
• Deallocates the memory of objects that are not marked as live.
• Is automatically run by the JVM and not explicitely called by the Java developer.  Unlike languages such as C++, the Java developer has no explict control over memory management.
• Does not manage the stack.  Local primitive types and local object references are not managed by the GC.

So if the Java developer has no control over memory management, why even worry about the GC?  It turns out that memory management is an integral part of an application's performance, all things being equal.  The more memory that is required for the application to run, the greater the likelihood that computational efficiency suffers. To that end, the developer has to take into account the amount of memory being allocated when writing code.  This translates into the amount of heap memory being consumed.

Memory is split into two types:  stack and heap.  Stack memory is memory set aside for a thread of execution e.g. a function.  When a function is called, a block of memory is reserved for those variables local to the function, provided that they are either a type of Java primitive or an object reference.  Upon runtime completion of the function call, the reserved memory block is now available for the next thread of execution.  Heap memory, on the otherhand, is dynamically allocated.  That is, there is no set pattern for allocating or deallocating this memory.  Therefore, keeping track or managing this type of memory is a complicated process. In Java, such memory is allocated when instantiating an object:

String s = new String();  // new operator being employed
String m = "A String";    /* object instantiated by the JVM and then being set to a value.  The JVM
calls the new operator */

IT jobs are without a doubt some of the highest paying jobs with information architects, data-security analysts and UX designers taking home $100,000 or more a year. But then again, these are high demand; high expertise jobs so don’t jump with joy as yet. But like every job and IT industry to be specific, not everyone commands such higher salaries. There are a large number of IT professionals who at some point of their career feel that their salaries have hit a standstill. Even if you are an IT professional and a great one at that, your technical expertise alone may not help you exceed the IT earning barrier. To continuously exceed your salaries, you need to work hard and smart. Here is how you can exceed the earning barrier in IT.

·         Gain Business Knowledge and Move Up The Management Ladder: IT departments for the most part are considered a part of “back office” operations. What this means is that despite being a core part of the business, IT professionals do not often get enough say in revenue generating components of the business and as a result seldom have a chance to take up senior management roles.  So if you do not want to stay content with a project manager or senior project management salary, invest time and money in gaining business knowledge. It could be through a formal business degree, online training courses or just by keeping your eyes and ears open while in the organization. Having the technical experience with business knowledge will instantly make you stand apart and open the doors for you to draw senior management salaries. For example, a survey conducted highlighted that CIOs were the biggest salary winners which clearly demonstrates the value of technical and business knowledge

·         Gain expertise on the “Hot” Technologies and Keep Learning: Say you are an expert in Java and draw a respectable salary in the industry. However, someone with less years of experience than you joins the organization and draws a higher salary than you! Why you ask. It could very well be because he/she is an expert in say big data technology such as Hadoop. Information Technology is one of the most dynamic industries with new technologies and languages coming up every now and then. When a new technology comes to the foray and gains traction, there is an instant demand-supply gap created which means that those with the specific skill sets are in a position to demand high salaries. If you have to break the IT earning barrier, always be ready to reinvent yourself by learning new technologies and this way you will be well positioned to jump on the high paying opportunities in the IT industry

·         Work On Your Own Side Projects: This one might seem controversial but let me clarify that I do not mean doing freelance work because even though your organization may never find out, it is ethically in breach of contract with your contract. If you have been lucky enough to be trained in some web based technologies such as Java, .NET or even HTML etc. spare sometime after office to build your own side projects. They could be very small projects tackling some problem that only you might have but there are multiple benefits of developing side projects. Worst case scenario, you will improve your technical skills. On the up side, you might end up creating your own business. A lot of technology start-ups were actually side projects the founders tinkered on with while they were employed full-time. You may not always succeed but there is no downside to the same