We changed our privacy policy. Read more.

New answers tagged

0

One thing that I learned from Herman Holtz's (Hermann Holz) many books on "consulting contracts" is the idea of task orders. An umbrella contract sets the ground rules for one or more individually-scoped-and-priced task orders to be issued during the fulfillment of the contract. It is further specified that all revisions must be accompanied by ...


0

Offhand ... "most likely, the PM already knows the answer." But, (s)he knows that your suggestions need more development: (s)he couldn't take it before other business stakeholders. Fair enough. For instance: "I recommend that requirements, designs, and code should undergo reviews." is actually quite generic. The same could be said of &...


0

It sounds like the PM is asking you for a cost/benefit analysis. Tests and reviews slow down the process of producing software (at least in the short term), which means they cost money. If you want to convince the PM that they're worth implementing you need to show that the expected value of doing them outweighs that cost. You don't need exact figures, but ...


2

Many similarly-structured projects – where legal contracts hold sway, adopt one or the other of two strategies: (1) Formal Change Orders: The parties must expressly negotiate each change to the contract. (2) Formal Burn-Limits: The parties may informally bargain within the scope of the contract so long as the total amount of money spent doing so does not ...


0

Risk management is identifying and evaluating the organization's risk and selecting and implementing measures to treat risk or loss exposures while risk register is a document or tool used to record numbers of risk exposures, regulate compliance and state the relevant information relating to risk such as nature of risk,mitigation and measure and who's ...


2

As per the wording in your question: And I got a feedback that solution design is approved but under one condition!! That to add 3 points from the last document I did analysis for. So it sounds like they have recognised that that their request is bigger than the original scope, and yet they want it for no additional cost. This should be seen as an ...


2

If you have a change process defined, and your customer is sidestepping the process to squeeze scope in without paying for the impacts, then you say no. You're a party to the contract and you get to say no if you think the contract is being violated. It's the job of the PM. EDIT to address comments: They are right to say the change is needed...if indeed it ...


2

Why do you want to reject what the customer is asking? If your contract or your way of working obliges you to turn away work that the customer wants and is presumably willing to pay for then perhaps your business model is broken and that is not the customer's fault. The second thing to think about is that on any project (I'm assuming software development) ...


0

If you are competing for resources, it is because you have not agreed with the other project lead what the split of resources should be. Your project documentation should define your resource requirements, including the finances, the equipment, and the people. If that isn't the case, then you have a hole in your documentation, so a first step might be to fix ...


-2

Everyone with an apparently different understanding of project requirements needs to be reminded both of the original, specific wording and of the usual interpretation in industry-standard custom and practice. If there are people who can't or won't accept that, either they need to attend some kind of group-think seminar to get their minds right, or they're ...


0

The benefits of reviews for requirements, designs, and code less bugs assumptions are reduced code can be easier to change more time to write better tests requirements are better understood common design mistakes can be avoided software that meets more requirements correctly delivery pace can be maintained and not slow down The biggest single advantage - ...


2

There should be a decision authority, like a steering committee, who allocates resources to programs and projects within its scope. If you're a project leader of a few of them, your task is to build a case for what you need. That same authority would also handle and provide solutions for those who are trying to consume more than what was allowed. You need to ...


1

How to successfully compete with other project leads for valuable resources? You don't. Resources (including people, who are not resources) should be managed based on company's interests (not business priorities, because they may differ). Granted, business priorities is one of the dimensions to consider. Unlike resources, however, people have aspirations. ...


0

Possible arguments: It is easier to fix issues if they are found earlier in the development process and reviews may draw out these issues Reviews could potentially reduce the need for re-work, which is a form of waste By finding issues earlier in the process you can help to de-risk the later stages of the work Reviews are a form of knowledge sharing


6

I think it is a very fair question for the PM to ask. Evaluating the proposed effort against its benefits, costs, and risks is proper leadership and management. If you have a proposal for testing, you ought to be able to articulate value. If you cannot, then do you truly understand the work? Testing is risk mitigation, and PMs own the responsibility to ...


1

I am going to answer this question more generically because deconflicting stakeholder issues should not require different methods based on who the stakeholders are or what the tasks are. Different opinions, interpretations, and perceptions are a given on any complex project so the team should have a process by which these issues are escalated, examined, ...


8

Modern testing is all about how you assist to "Accelerate the Achievement of Shippable Quality". Do your reviews help with accelerating? What metrics do you use to create proof of that? Testing helps with reducing risks, but at what cost? What is the return on investment. Overall I think the project managers question seems a very valid one. Wonder ...


3

I'm not sure that there is a good answer to the manager's question. In some contexts, having formal gate reviews may be beneficial. However, reviews tend to be after-the-fact inspections, which aren't the best way to build quality into a product. I'd recommend rethinking what you mean by "review". For example, the Three Amigos can help you during ...


5

If there are two stakeholders who have different understandings of the requirement, then there may be more. What about how you interpret the requirement, from the perspective of a tester? Or how about the customer? Or even the end-users of the product? If the requirement is ambiguous to the point where two people who (in theory, anyway) are working closely ...


7

What do you mean by "reviews" in this context? Many development teams do peer-reviews of code and analysis because they find that reviews improve productivity and quality. Many teams also make end-user reviews part of their Definition of Done for work. This is something the whole team should have an opinion on, not something you need to discuss ...


7

This is a great question. Several years back I analysed the bugs reported in a team and found that over half of them came about as a result of misunderstanding of requirements. Some things that can help to reduce this problem include: Have the team (QA, devs, PM, etc.) jointly add details to a requirement, so that they share a common understanding Using an ...


2

Welcome to PMSE! It's very normal for people to have different understandings of a requirement but what is interesting is that you haven't mentioned the person whose opinion matters most of all: the customer. The way to deal with your situation is to collaborate closely and frequently with your customer (sponsor / product owner / end-users), deliver results ...


0

In terms of QA, when a requirement is frozen, prepare your test cases and present them to the team. Everybody will see what they will build and/or receive and come up with questions & change requests before you start testing.


3

This is a difficult one to answer because there could be a lot that is not being said, however, based on what you are saying here is some guidance. TL;DR Projects are temporary organisations to deliver value and they run best on collaboration and influence. The best way to work with the project team is to ask them how can I better support the project ...


0

There are many different, necessary expert types to run a successful project, not just the single technical expertise that is part of the substantive work being performed. The larger the project, the more different types, including several technical types, that are likely required. It is interesting that you report being the only subject matter expert in the ...


Top 50 recent answers are included