Skip to main content

The R&D project manager

One of the most difficult tasks in any organization is the management of R&D activities.

These R&D activities are usually headed up by architects, developers, managers, and even executives. All of these people, at one time or another, may act as R&D project managers.

R&D project requires:


Research and development (R&D) include activities that companies undertake to innovate and introduce new products and services.

It is often the first stage in the development process.

The goal is typically to take new products and services to market and add to the company's bottom line.

R&D personnel were probably the first true project managers in the world.

Problems faced by R&D project manager:

    1) achieve an objective but lack of clear goals

    2) budget constraints

    3) resource constraints

    4) tight schedule and unrealistic timeline

Management Technique used by project manager for executing the R&D project:


Need to ask below questions for identifying R& Project:

  • What are the objectives of the project?
  • What is new about this project?
  • What methods are being used to carry out the project?
  • How generally applicable are the findings or results of the project?
  • What types of staff are working on the project?
  • How should the research projects are classified?

R&D project often involves managing usability, operability, reliability, maintainability and serviceability of the result product and the entry-exit criteria and their fulfillment for each sub-process in the total development process. 

The required level of usability, operability, reliability, maintainability and serviceability needs to be specified upfront in the product requirements to be built-in the product.

The development process control needs to be specified in the project requirements or methodology.


Comments

Popular posts from this blog

Certified Enterprise Architect Professional (CEAP) - Module 5 - Architecture Frameworks

Architecture Frameworks: An Architecture Framework is a theoretical structure that has the purpose of developing, executing, and maintaining an Enterprise Architecture. Advantages of EA framework: Simplify Breaks down areas of the business process Organise business components and create and identify relationships between business Determine the scope Customization in the existing framework Disadvantages of EA framework: Need to follow process Provides only direction and not information It's based on goal and objective Need creativity and proactive thinking Zachman Framework: The Zachman Framework is a widely used model in Enterprise Architecture (EA) that provides a structured way to classify and organize an organization's information infrastructure by defining different perspectives from various stakeholders, allowing for a holistic view of the enterprise and facilitating alignment between business needs and technology solutions; essentially acting as a template to organize arc...

Daily Agile Scrum stand-up meeting guidelines

Followers of the Scrum method of project management will typically start their day with a " stand-up meeting ". In short, this is a quick daily meeting (30 minutes or less) where the participants share the answers to the three questions with each other: • What did I accomplish yesterday?  • What will I do today?  • What obstacles are impeding my progress?  Some people are talkative and tend to wander off into Story Telling .  Some people want to engage in Problem Solving immediately after hearing a problem. Meetings that take too long tend to have low energy and participants not directly related to a long discussion will tend to be distracted. These are the minimum number of questions that satisfy the goals of daily stand-ups. Other topics of discussion (e.g., design discussions, gossip, etc.) should be deferred until after the meeting.  Here are few tips for running a smooth daily meeting:  • Everyone should literally stand-up and no one should sit down ...

Empiricism (Scrum)

Empiricism asserts that knowledge comes from experience and making decisions based on what is observed. Pillars of  Empiricism . Various practices exist to forecast progress, like burn-downs, burn-ups, or cumulative flows. While proven useful, these do not replace the importance of empiricism . In complex environments, what will happen is unknown. Only what has already happened may be used for forward-looking decision making. Each artifact contains a commitment to ensure it provides information that enhances transparency and focus against which progress can be measured: ● For the Product Backlog it is the Product Goal. ● For the Sprint Backlog it is the Sprint Goal. ● For the Increment it is the Definition of Done. These commitments exist to reinforce empiricism . The sum of the Increments is presented at the Sprint Review thus supporting empiricism .