5

Product is currently in beta stage and never been public, only client team and the team of testers have access to this. How often is the client checking in? Do you have regular reviews? You want the feedback loop short and actionable. The requirements are very much agile and I'm keeping hard to keep everything persistent during sprints and day to ...


4

Always Plan Based on Your Project's Available Resources I am trying to put together a plan comprising a list of deliverables (to be produce by patent attorneys), each with an estimated date. Although I have project management experience, I do not have patent application experience (first attempt at a patent). Even if you did have experience with patents, ...


4

TL;DR Should I add something to "Client Obligations" about code style? You can do this, but you may be measuring the wrong thing. This smells like an X/Y problem: you have a problem to solve with the deliverables hand-off, have decided that coding style is the thing that will fix the problem, and are now trying to solve for "coding style" rather than the ...


3

As it is a fixed-price arrangement I would expect that you have a payment plan or structure in place that means you pay most or all of the fees on acceptance of the finished product. Therefore you are somewhat covered here- if the third party does not produce acceptable work then you simply don't accept it and don't pay their fees. The key to making this ...


3

The communication gap I often see between a technical person and a non technical person is getting from technical component to the end business result. When requirements are being developed and identified, it starts with what you want to happen for the business, which is decomposed to a functional requirement, which is decomposed to a technical requirement, ...


2

Analysis When I saw the first component and compared it to the expected, I knew I had to change the way they were working because we had lost possibly half of the week making the developers work on something different from what I expected on that delivery. When you work with a third-party vendor, you can generally specify what will be provided and when ...


2

Think 'business person' instead of 'non technical person' If you have not read the business case for the project already, ask for it and get the tech team fully familiar with it. If you don't know why you are doing this project and what the Key Performance Indicators (KPIs) are, you cannot effectively communicate with the business people. I am trying to ...


2

TL;DR Sometimes the production of an artifact is the focal point of a process. Other times, artifacts are a byproduct of the process or they're not created at all. In some cases, it's simply a matter of perspective. For example, is a piece of working code an artifact, a change in product state, or the meeting of a requirement or goal? Pick any three. :) ...


2

Just store it in git, in a separate location. You're not likely to have capacity issues because of source code required for prototyping. But you do want to exclude it from statistics as it may not confirm to strict coding standards.


1

From your text I assume that: You mostly have issues with small scope / minor customization, which your customer keeps demanding from you to do for free. Your typical delivery tactics is to deliver the first project with fixed scope / fixed price, and then sell time-and-material consultancy services on top. You want to determine which scope belongs where. ...


1

The answer to your question needs to occur before you provided pricing. Within the contract, you would indicate who owns the what after the what is built. And then based on that you would price its development accordingly. So I would advise you not pushing forward the price at which you arrived until you answered this question with your client and get it ...


1

Documents live and die by organization and relationship, so the hierarchical approach scales better. For example: Earlier this year we made the AWS SDK developer guides available as GitHub repos (all found within the awsdocs organization) and invited interested parties to contribute changes and improvements in the form of pull requests. Today we are ...


1

In MsProject: First know that there is no way that you can put columns to right of gantt chart in MsP, other than that; You have to indent your deliverables in order for them to rollup. To do it first enter the deliverable name to a line, then enter tasks related to it just below it. Press "Indent Task"(Alt + Shift + Right) you can select multiple tasks ...


1

Even Agile can have some initial planning and artifacts produced. I described it here. So, it's totally ok, if your roadmap starts with "Onboarding and initial backlog creation" phase/sprint/milestone. And it is very helpful to avoid impression from your customer that you start working on features on 1st week of your project. So, in regular PM you can also ...


1

One option is to use git's branching functionality. When you run one of these prototypes, do it in a branch (like a topic branch). For most of these, they would then just sit in their own little branches, separate from the main/development branch. If you decide to keep and integrate the prototype code into the production code, all you need to do then is to ...


1

It's code, so use source control. I would hope that source control is being used regardless of whether it is a prototype or not. Personally I'd recommend using source control even for "proof of concept" and other quick test projects to figure out how to use or do something. As source control software is essentially an archive with version control, ...


1

Service and training are two examples. There is a state change-a customer being served and a change in knowledge or skill-without having a product being produced necessarily.


1

There really doesn't need to be a separate goal for accuracy and fraud prevention since these should be handled by standard business policies and procedures. This goal and the associated tasks can be combined in the main flow based on documentation of prior approvals, policy compliance, and employee's supporting documentation. (I've specified the ...


1

So many of these sorts of questions depend on what govenance your company sets out but Marv said it best. Think about what you need to achieve. For me (in my company) then the Project Initiation Document(PID) or Starter deck or whatever you call it is the main deliverable for this meeting. Before I go into a kick off I'm probably going to know what the ...


1

A Statement of Work should specify anything that matters to you. If programming style is on that list, there is nothing theoretically wrong with specifying it, although it opens up the risk of unintended consequences. Other responses have gone into that in more detail. In a company where I worked until recently, we got tired of web subsites being handed off ...


1

As software recommendation questions are discouraged, let's review what are good ways to present this information. Based on it, we can take this list to assess if a software is good or not for your needs. Investment Themes I'm afraid not quite used to this term, but as per THIS article, it seems to be a methodology (usually applied for Agile) to make sure ...


Only top voted, non community-wiki answers of a minimum length are eligible