This fits with my experience; I would include the following: What do the developers have to learn? New technology? New business domain? Are there new system i

This fits with my experience; I would include the following: What do the developers have to learn? New technology? New business domain? Are there new system interconnections? How many? How involved is the 'customer'? Who is the 'customer'? For B2B or enterprise software, do you have access to people who will actually be using your software? === A question I've been thinking about: Code, config, build and release pipelines, tests, documentation, etc are all the work product of software development, and those can be quantified (kind of). But what is the unit of work for software developers? I think it's the "try" - as in I had to try 100 different things to get this stupid thing to build. Those 100 things may have been in 2 logical work paths or 10 or 30. One path may have had 2 tries or 50. A path may have split into 2 or 3 or 10 other sub-paths.