This document summarizes an interview with Stefan Voxby, a project manager at Ericsson, about managing the "Cello 7 project" which involved developing a new hardware board. The project had 100 people and a 1 year timeline. Stefan was responsible for planning the project, allocating resources to teams, tracking progress in Microsoft Project, and managing risks such as component shortages. He found that having good relationships with coworkers and an established project methodology were important for success.
Context-driven testing is a software testing methodology that focuses on tailoring testing objectives, techniques, and documentation to the specific context of each project situation. The context includes factors like the people involved, goals, resources, and timelines. The key principles of context-driven testing are that practices depend on context, there are no universally best practices, collaboration is important, projects evolve unpredictably, products must solve problems, testing is challenging intellectual work, and effective testing requires judgment tailored to each context. Context-driven testing contrasts with approaches that focus first on standardized practices or documentation over project-specific needs.
Applying good context driven testing in an agile contextMarkus G辰rtner
油
This document discusses applying context-driven testing in an Agile context. It emphasizes that projects unfold unpredictably and practices must be tailored to their specific context. Good testing is a challenging intellectual process that requires judgment to do the right things at the right times through cooperative work across the entire project. People working together are the most important part of a project's context.
The document summarizes how companies and faculty can propose projects for Marquette University's senior design course. It explains that all engineering seniors are required to work on a year-long team project, with project ideas coming from sponsors or faculty. Teams of 4-5 students from different engineering fields work on each project. Sponsors provide a 1-2 paragraph description to recruit students. If a project is selected, sponsors meet periodically with the team and provide 1-4 hours of support per week. The goal is for students to experience an engineering project lifecycle while producing potentially useful work, though results cannot be guaranteed.
Prezentacja z 坦smego spotkania z cyklu Quality Meetup.
Autor: Micha Stryjak (QA Manager, PiLab SA)
Przez wiele lat ludzie starali si wskaza niezawodne podejcie do testowania. Nasz Go uczestniczy w wielu dyskusjach dotyczcych wy甜szoci jednej metody nad drug, kt坦re zwykle sprowadzay si do poszukiwania odpowiedzi na pytanie, czy jaka konkretna praktyka zmieni wiat test坦w na zawsze.
Ju甜 wiele lat temu Cem Kaner zauwa甜y, 甜e najlepsze praktyki goszone przez jego koleg坦w wykadowc坦w nie zawsze sprawdzaj si dobrze w rzeczywistoci. Czsto obserwowa jak procesy i narzdzia stosowane z powodzeniem, np. w startupach, nie sprawdzaj si w bankach lub bran甜y medycznej (i vice versa). Z biegiem lat Cem doszed do wniosku, 甜e coraz wicej os坦b ma podobne spostrze甜enia dotyczce najlepszych praktyk. Ludzie podzielajcy jego pogldy (najbardziej znani to James Bach i Bret Pettichord) twierdz, 甜e aby m坦c testowa dobrze, najpierw trzeba uwzgldni i przeanalizowa kontekst. Ich idee znalazy odwzorowanie w siedmiu zasadach, kt坦re dzisiaj stanowi podstaw podejcia Context足-Driven Testing (CDT). Na spotkaniu Micha opowie nam o podstawach CDT oraz podzieli si pomysami, jak mo甜na wdra甜a wspomniane siedem zasad w 甜ycie.
Strategizing to build a perfect test environmentEnov8
油
Test environment management has become a vital part in keeping any organisation together. To fetch some in-depth learning environment, what it is and how exactly it works, there is a use case developed. Summing up, the test environment brings down all the aspects of the organisation together like project managers, test managers, developers, and most importantly the environment managers.
The document discusses key principles of applied software project management including responsibility, authority, and accountability. It emphasizes the importance of delegation, transparency, managing senior managers and the organization, and managing the project team. Some best practices discussed are establishing guidelines, sharing information, addressing problems early, and avoiding micromanagement.
Scope creep refers to an increase in project scope from what was originally agreed upon and occurs when the project scope is not properly defined, documented, or controlled. It is generally considered negative and should be avoided. Scope creep can be caused by poor project management, lack of change control, underestimating complexity, and stakeholders remaining uninvolved. Consequences of scope creep include missing deadlines, increased costs, low return on investment, and potential project cancellation or failure. To avoid scope creep, it is important to get scope approved by all parties, have a detailed understanding of vision, use a work breakdown structure, and have good communication plans. While challenging, scope creep can also trigger innovation.
DevOps is the movement to bring Development and Operations closer communicate and collaborate across Dev and Ops. DevOps is thinking long-term, it combines together all the best practices available like automation, agile and more.
Three key skills for engineers are knowledge, experience, and intuition. Knowledge refers to principles and tools used for analysis, experience comes from both successes and failures, and intuition develops from extensive knowledge and experience to help guide choices. Engineering design aims to meet needs through products, processes, or software and involves experimentation, testing, and creativity.
Five development practices compose the core of Extreme Programming (XP)automating the build for continuously integrating software as it is written, collaborating with team members through pair programming, practicing agile design skills that enable testability, using test first development to drive design, and refactoring code to reduce technical debt. Together, these five technical disciplines are proving to be essential for sustained success with agile development. However, many teams havent been exposed to the benefits of these practices or understand how to use them effectively. David Bernstein explores these engineering practices and their use in reducing risk and building quality in at every level of the development process. He makes the business case for these practices by showing how they address the inherent risks and challenges of building software. David then examines how XP practices address the core issues of software development by helping us build the right thing and build the thing right.
Why projects are causing your organisation staff salary costs to go up Barry Hodge
油
The document discusses why organization staff salary costs are increasing due to projects. It provides two steps to stop costs from rising: 1) Include the cost of internal staff time worked on projects in project budgets at a fixed daily rate. This allows substituting external staff if needed without exceeding budgets. 2) Use a gated approach to project delivery that progresses in steps, allowing projects to be stopped before too many resources are spent if not viable. Doing so can prevent projects from going over budget or increasing long-term organization costs.
Fabian Scarano - Preparing Your Team for the FutureTEST Huddle
油
EuroSTAR Software Testing Conference 2008 presentation on Preparing Your Team for the Future by Fabian Scarano. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Why social housing transformation projects get stuckBarry Hodge
油
This document discusses why social housing transformation projects often get stuck and provides 3 steps to help get them unstuck. It explains that projects get stuck due to the unique operating environment of social housing providers, limited funding, and not enough resources. Specifically, it identifies the "yes effect" where people overcommit and the "magpie effect" where people lose interest in ongoing projects when new shiny ones start. The 3 steps to get projects unstuck are: 1) Break large projects into smaller ones, 2) Make a prioritized list of all projects, and 3) Use a gated approach to deliver projects in stages.
This document introduces Project Rescue, a project management consulting service led by Senior Project Director Allen Goldberg. It summarizes that Allen has experience turning around troubled projects in various industries, getting them back on schedule and budget through assessing problems, reworking plans and communication, and ensuring user adoption. His customized methodology focuses on the specific project needs. Project Rescue is presented as a solution for companies struggling with projects that are over budget, behind schedule or facing other issues.
This presentation provides an overview of the content and features of the Social Impact Analysis course delivered on Efiko Academy in partnership with Social Value International. It is meant for people and organisations who seek to develop impact measurement and impact management skills.
2009 Top Ten Obstacles To Project SuccessLou Gasco
油
This presentation is intended for use by Project Management, Program Management, or Senior I.T. Leadership to understand the nature of the most common obstacles found by project managers on typical projects.
In order to satisfy the various deadlines that are associated with a building project, there are multiple teams, each of which plays a unique role. Every team has a project manager who is responsible for coordinating with the other teams and maintaining transparency. The following are some of the responsibilities that are handled by the most qualified residential contractors in Delhi.
In this presentation we will talk about effective ways, overview and concept of Managing IT Projects.
To know more about Welingkar Schools Distance Learning Program and courses offered, visit:
http://www.welingkaronline.org/distance-learning/online-mba.html
importance of resources allocation in formal method of software engineering ...abdulrafaychaudhry
油
This document discusses key concepts related to project management including resource allocation, software risks, differences between products and projects, discount factors, net present value, and net profit.
The main points are:
1) Resource allocation in project management is important for planning, scheduling, and controlling workload to improve team effectiveness. It involves identifying and tracking resources like budget, tools, and time.
2) The top five software risks are inherent schedule flaws, requirements inflation, employee turnover, specification breakdown, and poor productivity. Agile methods aim to mitigate these risks through practices like iterative planning and prioritization.
3) The key difference between a product and project is that a product is manufactured and sold while a project is built to
The document provides guidance on project management procedures. It was written by Dr. Andrew Kimmance, who has over 30 years of experience in civil engineering and construction project management. The guidance covers the typical project life cycle, which begins with an initiation phase involving defining the project objectives and scope, appointing a project team, and gaining approval to begin detailed planning. It emphasizes the importance of the initiation phase in setting up the project for success. The document then provides tips and templates for properly initiating projects and taking them through the project life cycle.
The document provides guidance for participating in a project management training session, including instructions to mute videos, speak one at a time, participate constructively, and use English as the medium of interaction. It then defines project management, explains the importance of project management for achieving goals on time and on budget. It discusses the project life cycle including initiation, planning, execution, and closure phases.
Introduction to Project Management (workshop) - v.1Mena M. Eissa
油
This document provides an introduction to project management concepts. It begins with introductions from the presenter and the audience. It then defines key project management terms like project, project management, stakeholders, roles, scope, requirements, deliverables, change, risk and lessons learned. It discusses the triple constraints of scope, time and cost. It also outlines the typical project lifecycle phases of initiating, planning, executing, monitoring/controlling and closing. The document concludes with discussing next steps like certifications and tools to use in project management.
A Practical Approach Of Teaching Software EngineeringAmy Cernava
油
This 3-month university course aimed to provide students with practical software engineering experience through a real-world project. 12 students developed a tool called APE in teams over 5 phases. The initial plan proved overly optimistic and delays in analysis and design meant cutting functionality. Students gained experience in communication, technical challenges, and the software process through this project. Both students and supervisors learned important lessons about project planning and management.
The document discusses the importance of project scope and work breakdown structures (WBS) for defining project goals and tasks. It notes that a project scope statement establishes the expected results, constraints, and assumptions for a project. It also warns that creating project tasks without input from the entire team can result in an ineffective approach. Additionally, the document states that a WBS allows team members to have clear assignments while avoiding work that is too time-consuming. Finally, it reflects on how developing a student life scope project helped the author practice project management and time management skills.
DevOps is the movement to bring Development and Operations closer communicate and collaborate across Dev and Ops. DevOps is thinking long-term, it combines together all the best practices available like automation, agile and more.
Three key skills for engineers are knowledge, experience, and intuition. Knowledge refers to principles and tools used for analysis, experience comes from both successes and failures, and intuition develops from extensive knowledge and experience to help guide choices. Engineering design aims to meet needs through products, processes, or software and involves experimentation, testing, and creativity.
Five development practices compose the core of Extreme Programming (XP)automating the build for continuously integrating software as it is written, collaborating with team members through pair programming, practicing agile design skills that enable testability, using test first development to drive design, and refactoring code to reduce technical debt. Together, these five technical disciplines are proving to be essential for sustained success with agile development. However, many teams havent been exposed to the benefits of these practices or understand how to use them effectively. David Bernstein explores these engineering practices and their use in reducing risk and building quality in at every level of the development process. He makes the business case for these practices by showing how they address the inherent risks and challenges of building software. David then examines how XP practices address the core issues of software development by helping us build the right thing and build the thing right.
Why projects are causing your organisation staff salary costs to go up Barry Hodge
油
The document discusses why organization staff salary costs are increasing due to projects. It provides two steps to stop costs from rising: 1) Include the cost of internal staff time worked on projects in project budgets at a fixed daily rate. This allows substituting external staff if needed without exceeding budgets. 2) Use a gated approach to project delivery that progresses in steps, allowing projects to be stopped before too many resources are spent if not viable. Doing so can prevent projects from going over budget or increasing long-term organization costs.
Fabian Scarano - Preparing Your Team for the FutureTEST Huddle
油
EuroSTAR Software Testing Conference 2008 presentation on Preparing Your Team for the Future by Fabian Scarano. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Why social housing transformation projects get stuckBarry Hodge
油
This document discusses why social housing transformation projects often get stuck and provides 3 steps to help get them unstuck. It explains that projects get stuck due to the unique operating environment of social housing providers, limited funding, and not enough resources. Specifically, it identifies the "yes effect" where people overcommit and the "magpie effect" where people lose interest in ongoing projects when new shiny ones start. The 3 steps to get projects unstuck are: 1) Break large projects into smaller ones, 2) Make a prioritized list of all projects, and 3) Use a gated approach to deliver projects in stages.
This document introduces Project Rescue, a project management consulting service led by Senior Project Director Allen Goldberg. It summarizes that Allen has experience turning around troubled projects in various industries, getting them back on schedule and budget through assessing problems, reworking plans and communication, and ensuring user adoption. His customized methodology focuses on the specific project needs. Project Rescue is presented as a solution for companies struggling with projects that are over budget, behind schedule or facing other issues.
This presentation provides an overview of the content and features of the Social Impact Analysis course delivered on Efiko Academy in partnership with Social Value International. It is meant for people and organisations who seek to develop impact measurement and impact management skills.
2009 Top Ten Obstacles To Project SuccessLou Gasco
油
This presentation is intended for use by Project Management, Program Management, or Senior I.T. Leadership to understand the nature of the most common obstacles found by project managers on typical projects.
In order to satisfy the various deadlines that are associated with a building project, there are multiple teams, each of which plays a unique role. Every team has a project manager who is responsible for coordinating with the other teams and maintaining transparency. The following are some of the responsibilities that are handled by the most qualified residential contractors in Delhi.
In this presentation we will talk about effective ways, overview and concept of Managing IT Projects.
To know more about Welingkar Schools Distance Learning Program and courses offered, visit:
http://www.welingkaronline.org/distance-learning/online-mba.html
importance of resources allocation in formal method of software engineering ...abdulrafaychaudhry
油
This document discusses key concepts related to project management including resource allocation, software risks, differences between products and projects, discount factors, net present value, and net profit.
The main points are:
1) Resource allocation in project management is important for planning, scheduling, and controlling workload to improve team effectiveness. It involves identifying and tracking resources like budget, tools, and time.
2) The top five software risks are inherent schedule flaws, requirements inflation, employee turnover, specification breakdown, and poor productivity. Agile methods aim to mitigate these risks through practices like iterative planning and prioritization.
3) The key difference between a product and project is that a product is manufactured and sold while a project is built to
The document provides guidance on project management procedures. It was written by Dr. Andrew Kimmance, who has over 30 years of experience in civil engineering and construction project management. The guidance covers the typical project life cycle, which begins with an initiation phase involving defining the project objectives and scope, appointing a project team, and gaining approval to begin detailed planning. It emphasizes the importance of the initiation phase in setting up the project for success. The document then provides tips and templates for properly initiating projects and taking them through the project life cycle.
The document provides guidance for participating in a project management training session, including instructions to mute videos, speak one at a time, participate constructively, and use English as the medium of interaction. It then defines project management, explains the importance of project management for achieving goals on time and on budget. It discusses the project life cycle including initiation, planning, execution, and closure phases.
Introduction to Project Management (workshop) - v.1Mena M. Eissa
油
This document provides an introduction to project management concepts. It begins with introductions from the presenter and the audience. It then defines key project management terms like project, project management, stakeholders, roles, scope, requirements, deliverables, change, risk and lessons learned. It discusses the triple constraints of scope, time and cost. It also outlines the typical project lifecycle phases of initiating, planning, executing, monitoring/controlling and closing. The document concludes with discussing next steps like certifications and tools to use in project management.
A Practical Approach Of Teaching Software EngineeringAmy Cernava
油
This 3-month university course aimed to provide students with practical software engineering experience through a real-world project. 12 students developed a tool called APE in teams over 5 phases. The initial plan proved overly optimistic and delays in analysis and design meant cutting functionality. Students gained experience in communication, technical challenges, and the software process through this project. Both students and supervisors learned important lessons about project planning and management.
The document discusses the importance of project scope and work breakdown structures (WBS) for defining project goals and tasks. It notes that a project scope statement establishes the expected results, constraints, and assumptions for a project. It also warns that creating project tasks without input from the entire team can result in an ineffective approach. Additionally, the document states that a WBS allows team members to have clear assignments while avoiding work that is too time-consuming. Finally, it reflects on how developing a student life scope project helped the author practice project management and time management skills.
Mark Spanos has over 30 years of experience in project services and project delivery management. He began his career in the late 1980s and has worked extensively in the field across multiple international locations and industries. Spanos focuses on applying an authentic and human approach to empower project teams to achieve and surpass goals through collaboration. He has a track record of successfully leading major projects valued between $250 million to $5.6 billion on time and on budget.
Mark Spanos has over 30 years of experience in project services and project delivery management. He began his career in the late 1980s and has worked extensively in the field across multiple international locations and industries. Spanos focuses on applying an authentic and human approach to empower project teams to achieve and surpass goals through collaboration. He has a track record of successfully leading major projects valued between $250 million to $5.6 billion on time and on budget.
Top Project Management Best Practices.pdfOrangescrum
油
Project management best practices will enable you to deliver your projects successfully. Through effective project management practices, businesses can improve the performance of the team to become faster, better and more efficient when compared to their previous results.
The document discusses software project management and provides 20 project management proverbs. It then defines what a project is and explains that projects have timeframes, require planning and resources, and need evaluation criteria. Finally, it discusses what a project manager does, including developing plans, managing stakeholders, teams, risks, schedules and budgets.
A project has several key attributes that distinguish it from regular day-to-day work: it is temporary in nature with a defined start and end date, it is unique and aims to create a new product or service, and it focuses on achieving specific goals. In contrast, regular operations are ongoing and repetitive without a clear end. Projects require planning, organizing, and allocating dedicated resources to accomplish their goals by a set deadline, while ensuring quality and managing risks. They involve coordinating a team using a structured approach to balance time, resources, results, and customer satisfaction.
The document provides guidance on conducting a Hazard Identification (HAZID) study for a major project. A HAZID study aims to identify potential hazards early so they can be eliminated or reduced. The summary includes:
1) A HAZID study should involve key project personnel and be conducted early in the design phase to identify hazards that can be designed out.
2) The outcome of the HAZID study is a hazard register that informs safety and environmental requirements and can be used to design out identified hazards.
3) Conducting the HAZID study requires brainstorming potential hazards using techniques like checklists, what-if analysis, and reviewing historical incidents to populate the hazard register.
This document discusses tools and techniques for managing projects that encounter problems and become "red" or off-track. It provides two case studies of implementing Oracle ERP projects and discusses lessons learned. The objectives are to familiarize audiences with readily available tools to get projects back on schedule, such as enhanced communication, examining the "triple constraints," breaking projects into smaller phases, and reanalyzing and mitigating risks. Keywords include risk identification/mitigation and early warning signs of project issues.
1. The document provides 10 tips for effective project management. It discusses the importance of time management, identifying project requirements, providing regular updates to stakeholders, communicating with the project team, defining critical milestones, evaluating the project, keeping skills up to date, tapping team strengths and weaknesses, using project management tools, and managing potential risks.
2. Key aspects highlighted include planning each day, identifying roles and tasks for team members, informing stakeholders of updates and addressing any delays or problems, reviewing all aspects of a project for future learning, and identifying risks that could threaten the project's progress.
3. Effective project managers organize their time, communicate clearly with stakeholders and their team, evaluate both successes and areas for improvement, and
Thesis writer, Dissertation writer, Plagiarism Free Dissertation writing services.
The difference between project planning stages or phases and project life cycle is very thin. The project stages are just the stages through which every project has to pass. On the other hand, the project life cycle is a continuous set of activities that have to be performed in a logical sequence in order to best achieve the business objectives
The document discusses project management frameworks and the components of managing an ICT project. It begins with defining what a project and project management are. It then discusses two prominent project management frameworks: PRINCE2 and PMBOK. The sessions cover the project management cycle including initiation, planning, execution, and closure. It also demonstrates project management software for documentation and work planning.
1. Project management
Douglas lsaksson
Master of Science student, Royal Institute of Technology
Stockholm, Sweden
douglasi@kth,se
Abstract
In this paper, we will discuss a proiect through the initial
phases and the evaluation process from a proiect manag-
er's point of view. Laying the foundationfor this article is
the development of a hardware platform, the "Cello 7
project". Led by the former KTH student nowadays expe'
rienced project manager at Ericsson Stefan Voxby, gladly
taking the opportunity of sharing his knowledgu to the
coming generation.
INTRODUCTION
To get a good insight of the real work of a project manager
we were offered a chance to make an interview with an
Ericsson employed Project manager, Mr. Stefan Voxby at
Ericsson CPP (Cello Packet Platform) facilities in lvsjO.
Stefan was assigned as a subproject manager for the "Cello
7 project" involving a total of 100 people working during
the 1 year development.
Figure 1. Stefan Voxby outside Ericsson CPP in Alvsj旦
PLANNING
The goal of the project was to design, test and produce a
new hardware board. Time was the most criti cal factor in
this proj ect. Ericsson had to surpass competitors increasing
quality and performance by upgrading their current hard-
ware boards.
Stefan was appointed the project in the planning phase and
as a first stage he had to gather human resources into teams.
From there the specialist from each team made an imple-
mentation proposal. The proposal contains afi estimate of
how much time it will take to achieve the functionality and
quality needed for the product. The project manager san
on Ericsson CPP
Sebastian Jacobsson
Master of Science sfudent, Royal Institute of Technology
Stockholm, Sweden
sebjac@klh.se
then use this as a basis for his Project Plan. An integration
plan was then created to indentiff where the project had its
dependencies. Examples of this would be when the proto-
type had to be delivered to the test department or when the
project will get delivery from the component factory.
Since this was a hardware project there were potentially a
lot of practical problems. Prototyping in itself can be very
problematic and that has to be accounted for in the planning
stages of the project.
A first for Stefan in this project was using Microsoft
Project to keep track of the progress and identifying the
critical line so the activities could be optimized.
Each week Stefan would gather all his team leaders to get
an update on the project'S progress and import that into
Microsoft Project.
However it is common within Ericsson that each subproject
managerlteam leader can use whatever planning me-
thod/tool they want fbr their part of the project as long as
they follow the integration plan.
Stefan encourages his team leaders to state the resources
they want as a part of their team. He then goes to his Line
Manager and specifies the people he wants for his project.
This way he hopes that he can increase working efficiency.
However exact resources are usually hard to get hold of
since a lot of things can get in the way, other projects might
have a higher priority allocating the first choice resources
or the named resource might be unavailable due to sickness
or childcare etc.
There are always critical resources and it's always a task
for the project management to allocate these people to the
right activity.
RISK MANGEMENT
One important step that can be a real asset to entire proj ects
is the risk handling. If managed properly it can reduce risks
to avoid delays before they occur. A normal way of work-
ing is the mini risk method, however other methods could
be applied depending on the consequences, an example
would be time based risks. It is always important to keep in
mind that premier competence, risk and measures stays on
the level it concerns. Working the risks up to the top level
hierarchy is the 10 most crucial risks, where they can dep-
loy action measures.
Looking back at the Cello 7 project a risk that occuffed was
component shortage. That was a risk on the hardware level
thatwould delay the entire project, but was prevented using
good risk measures.
The process leader, in charge of the risk meeting (not nec-
essarily the project manager) has to make sure the risks are
weighted depending on probability and consequence. Risks
2. like fire in the f辰cilities has to be accounted for but they are
usually not identified during the meeting since the risk is
not directly related to the proj ect. Sickness or employment
loss is a crucial risk for all projects in Ericsson but have
measures on a different level, such as healthcare programs
with coaches etc., just to keep employees healthier and
makes Ericsson a more attractive employer.
PROJECT MODEL
Erissson follows the project model PROPS, developed by
Ericsson in the late 80's. Ericsson has regular checks to
make sure the organization follows the PROPS methodolo-
gy to keep certification standards. Stefan feels that it is
crucial for the project to have a predefined working metho-
dology to avoid unnecessary conflicts. Stefan has some
experience from working with other project models though
he has come to the conclusion that they are fundamentally
the same.
PROJECT ADMINSTRATION
What Ericsson looks for in a good project manager is broad
knowledg. area and that he/she has good social compe-
tence. The most impoftant feature of a successful project
manager is good relations with coworkers.
As a project manager you got to have advance planning
skills to let your mangers know when problems will arise.
A good relation with your above management is also
needed so you don't cover-up any problems. This is also
needed with your team leaders. They usually know the
resources needed to make the project a success which
makes your job a lot easier.
PROJECT ANALYSIS
The experience evaluation in the project took part even
befbre the flnish line was passed. The decision was made
on pupose by Stefan just to make sure that all recourses
could participate.
One experience he gained from Cello 7 was that Microsoft
Project was too much of a work burden in comparison to
what it contributed with. However it did not affect the im-
plementation section of the project. For the next project he
feels it's better to have fewer activities in the overall plan
and leave the detailed activities planning to the team lead-
ers. At the end of the interview we asked Stefan for some
tips on project management.
o His best tip as a project manager is to have a good rela-
tionship with your coworkers. If people feel they can
come to you and talk about anything you will know
every problem.
. A big part of having a good relationship is to have face
to face meetings, especially with employees working on
other locations. I)o not be afraid to travel because it is
always better to have a met the person in question, just
remember that all your travels will come with a cost.
Make sure that you really have a purpose and that you
can contribute with something.
o Get to know the working procedures at your firm, it can
often be defined but it's not always followed.
. Don't be afraid to try different projects that you aren't
familiar with. Example. If you are, a SW project manag-
er don't be afraid to try HW projects. This way you can
relate to the HW manager later on in your career.
ACKNOWLEDGMENTS
Special thanks go out to Stefan Voxby Project Manager at
Ericsson CPP in lvsj旦 for sharing his valuable time with
us, to be able to have this interview.