Skip to main content

Velocity and Burn Rate Budget

This is a great summary of where to get to in how you budget projects.

http://www.agileadvice.com/2011/02/04/agilemanagement/calculating-a-budget-for-an-agile-project-in-six-easy-steps/

Most importantly,
Using the definition of “done” add pre- and post- Iteration budgets
Every agile team is supposed to be “cross-functional” but in reality, there are limits to this.  For example, in most software project environments, teams do not include full-time lawyers.  This limited cross-functionality determines what the team is capable of delivering in each cycle – anything outside the team’s expertise is usually done as either pre-work or after the iterations (cycles) are finished.  Sometimes, this work can be done concurrently with the team.  In order to understand this work, it is often valuable to draw an organization-wide value stream map for project delivery.  This map will show you the proportion of time spent for each type of work in the project.  Subtract out all the work that will be done inside the agile team (their definition of “done”) and you are left with a proportion of work that must be done outside the agile team.  Based on the proportions found in the value stream map, add an appropriate amount of budget based on the project’s cycle labor costs.

Comments

Popular posts from this blog

Microservices Design Patterns

functional decomposition or domain-driven design well-defined interfaces  explicitly published interface  single responsibility principle potentially polyglot http://blog.arungupta.me/microservice-design-patterns/ http://blog.arungupta.me/microservices-monoliths-noops/ https://go.forrester.com/blogs/13-11-20-mobile_needs_a_four_tier_engagement_platform/ three-tier architecture — presentation, application, data vs. 4 tier -- client, delivery, aggregation, services

Dockercon 2021

 Dockercon 2021 Replay presentations ex:  https://docker.events.cube365.net/dockercon-live/2021/content/Videos/zo9AAafDLCPRv2rom https://github.com/docker/roadmap/issues/201 https://aws.amazon.com/ecs/anywhere/ https://cloud.netapp.com/blog/aws-cvo-blg-amazon-eks-anywhere-and-ecs-anywhere-multicloud-services https://docs.docker.com/cloud/ecs-integration/ https://github.com/GoogleContainerTools/skaffold https://docs.docker.com/compose/profiles/ https://docs.docker.com/compose/compose-file/compose-file-v2/ Lessons Learned With Dockerfiles and Docker Builds https://docs.docker.com/develop/develop-images/build_enhancements/  &  https://docs.docker.com/buildx/working-with-buildx/ "Java 11 is first version that is fully 'container aware'." As in it respects cgroups.  Docker Playground https://labs.play-with-docker.com/ Compiling to Containers with BuildKit https://github.com/agbell/compiling-containers https://earthly.dev/

Build software like you build houses

Interfaces facilitate visibility. Software is the only engineering practice that doesn't allow runtime visibility to end-user. If this were true for construction, it would mean your builder would have to live with you for you to even guess what the problem is. https://vimeo.com/221049715 https://github.com/stripe/veneur