Nueronic Consulting

Interesting,watch the video.

A lot of reasons have been mentioned over time regarding why a certain IT project have failed. One of those reasons is that roles and responsibilities are not defined correctly within a team. It doesn’t matter how big or small your project is-although some claim that when the project is larger things get complicated and are more confusing for project members. That is partially true. However although small teams and smaller project’s are more flexible and easier to manage when it comes to project roles and responsibilities It does get complicated especially when team members are assigned multiple roles within a team.
So within a project well defined roles, responsibilities and boundaries should be well defined. As a summary, you should focus on having clear definitions and understanding of the following:
• Client(s). These are the beneficiaries of the project, of the outcome that the project will deliver (e.g a software product).They are the people for which the project is being build for, sometimes they are the people will fund the project, put forth the requirements and accept the project. These people in some organisations are called customers.
• Project Director. The head of the project. Sometimes in big organisations the role between project manager and client is loosely defined-leaving the project manager crack on with the project and the project director deal with the client, the overall project strategy and corporate politics.
• Project Manager. The PM has the functional responsibility of managing the entire project. This includes, planning, risks, resources, project tracking, managing the team, the deliverables, quality, project scope, budget and timeline.
• Project team. The team consists of the resource that is assigned to work on a specific project. They are responsible for understanding what is to be delivered, what work is required, to provide estimations for the deliverables and keep the PM up to date on projects slippage, scope creeps etc. The team can consist of business analysts, developers, testers, designers etc.
• Project sponsors. The sponsor is a complicated concept. It is usually valid when it functions within an organisation. The sponsor is the person who has the ultimate authority over the project. The sponsor is the “point of sign off” for project changes, scope changes, releases (based on corporate strategy). Sponsors are responsible for the project at a higher level than the project manager and specifically on the project’s benefits to the organisation and how the project is aligned with the overall business.
• Stakeholder(s). The people who have an interest and will be directly affected by the project and its outcome. Stakeholders can be internal or external and this can include, clients, company employees, suppliers and vendors, investors, government etc.
• Users. AKA the end user. These are the individuals that will in effect use the deliverables of the project. Their responsibilities are varied including, defining requirements, participating in project meetings, change requests, testing of deliverables etc.

So, i have to admit i am probably one of the first people that downloaded and tested IE7. I was never really a fan of Firefox, and i have to admit i never had anything against it anyway. I am not into the whole Microsoft is evil open source rules type of thing and probably never will be. I like both and i use each technology whenever it suits me and whether a project or client demands it. But lately i had enough with IE7. if i load more than 5-6 tab’s it crashes, it just crashes. I haven’t looked for any updates or anything of the sort. Thanks Microsoft…..

Well i have been using Firefox lately and it works fine, no problems no crashes…until the problems are fixed I’ll keep IE 7 usage to a minimum