2

1) I'd suggest Delivery Plans, that helps you have a look at multiple projects/organizations, but works well if you set iterations. It's free for Azure DevOps. 2) You could set different capacity based on the planned deliveries, and allocate more resources on certain projects when you need it.


1

Thearot is taking a practical and technical approach, I would like to focus on what to test first. Ask yourself what you are afraid of to break. Your application is a relational database application, so everything can be measured by the state of your database. I would create some data bases with states to start out with. Then perform some operations and ...


1

You need a test environment, where the solution can be executed without affection whatever is in production. If they have a procedure for that, somebody can do it for you, otherwise, you got to figure it out. And I suspect this case will be on the figure out side. Set up the test environment That test environment include a database. You can set up a local ...


1

Just imagine a simple case. As a part of your task/ticket, you need to add some extra fields to class User plus some extra validation stuff. During the development, you found some unused directives in some other classes, so you decided to remove them to keep application code cleaner... I'd suggest that the reason for your question is because you are asking ...


1

When separating a big project into smaller ones, you HAVE to think about how that project will be tested. In practice, by separating big project into separate development/build projects, you have to assume those projects need to be independent of where they are used. And that they have completely separate lifecycle from the upstream dependencies. Basically, ...


1

A PR should be for one project only Updates to a package should be separate to updates to the consumer of the package. If there is a bug in DAL, then it should be fixed in DAL, a PR triggers the build and its version bump, and a new package appears. Now the consuming application can pull the package, and perform any associated updates. This is passed off ...


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