Stack Exchange Network

Stack Exchange network consists of 175 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.

Visit Stack Exchange
17

What is the MMM First I want to explain the context for Brook's Law. What was the assumption that made him create it back in 1975? A Man-month is a hypothetical unit of work representing the work done by one person in one month; Brooks' law says that it is impossible to measure useful work in man-months. source: https://en.wikipedia.org/wiki/...


14

Being a consultant I am contractually obliged to answer, "it depends". With that out of the way, I can actually answer your question. What does it depend on? Well, that could come down to what your boss thinks about DevOps: If your boss has heard of the term, via their obsession with CIO.com maybe, then ask them what they think it means. From there work ...


12

There are two types of work: Exploitation - Well defined work that can be easily divided into well-defined stages, where each stage can be learned and mastered on its own and handover between stages does not require communication. Exploration - Undefined work, which requires learning and experimentation to accomplish each stage and handover between stages ...


9

IMHO the comment is a bit misleading, in the sense that a chef is the boss of the kitchen mixes up and/or attempts to compare the unique leader/chef role (in French, chef literally means chief/boss/leader) with the expertise required to fill that role. By contrast, the full-stack developer is just an expertise, it is not a unique role. If I'm not mistaken ...


9

There are four main reasons why you can feel your team is understaffed: Poor organization and planning of work Doing work someone else should be doing Doing work that should not be done at all Being actually understaffed Start with a review of the first three points. Read the Phoenix Project on ideas how to do the first. Ask yourself for every task you ...


8

You don't. Despite your enthusiasm about DevOps, non-tech bosses don't really share your fascination with the techie lingo. First, show your bosses the benefit of a small pilot projects you have done. Collect some useful data points to prove your case. (Found this question that could help: What are some methods to measure the ROI for DevOps?) Next, tell ...


8

A value stream is a process that adds value to a collection of things that have less inherent value. The canonical example there is an assembly line. I have little interest in a disconnected collection of parts (steering wheel, shifter, gas pedal.) On the other hand, I'll pay good money for a car. Car manufacturers add value to the parts in the form of ...


8

Background: Besides for providing support to our current infrastructure and to our Developers, we do monthly planning as a DevOps team for what we want to accomplish on top of helping dev teams within sprints and new projects that are launched. However, during the month we often notice extra things that need to be done and improved, which we then add to our ...


7

Probably not the answer that you're looking for, but an answer nonetheless :) Learning about docker and its deployment methods could actually be included in the business requirements by making it part of the project or team development environment, just like the code language(s), version control system, compilers, test infrastructure, etc - to work in that ...


6

Adam Smith did not need to consider passing of information from one stage to another. This is a critical part of any significant IT project. So a fullstack developer has the significant advantages that: they don't have to talk to anybody in another department to get things done they don't have to wait for those other people to get around to it there's ...


6

What is Value Stream Mapping A Value Stream Map is a representation of the flow of work, inventory and information from supplier to the customer through your organization. The VSM enables you to see at a glance where the delays are in your process, any constraints and excessive work or inventory. For IT organizations, one common notation is that inventory ...


6

I'll give you my perspective. Developers should care about docker as there are other developers who are willing to use docker and have already built an expertise in it. They are willing to take up the roles of a DevOps engineer along with being a developer. So the Ops part of DevOps is what they are now building expertise on. These days, you'll find more ...


5

Truth would be that should not happen in a DevOps environment . Your "project" will probably use Agile concepts, but there's nothing in DevOps telling how a project has to be run because DevOps is product centric (more details on the blog post and with search on this term). "DevOps" is about breaking silos and have a team composed of developers, architects, ...


5

It is not about Docker or any other containerisation technologies out there. Containers like Docker, rkt, etc. are just way of delivering your application in similar fashion to static binary. You are building your deployment that it contains everything it need inside and end user doesn't need anything more than runtime. These solutions are similar to fat ...


5

I'll add an answer of what my solution is so far, but I'm still really interested in hearing how other organisations are solving this problem and the best practices they have. To resolve the issue of not having a consistent base to create projects for, my idea is to create a repository (repositories?) of boilerplates/templates and use cookiecutter as a tool ...


5

I actually take a page from the SRE Handbook on this one, which I think is very relevant. DevOps specialties are not meant to grow horizontally with an organization. Rather, if you see that things aren't getting done then it's a signal you're not properly empowering developers to self-service. Evaluate your processes and see how they align to the commonly ...


4

I assume this team of two is going from project to project and establishing DevOps stuff there (creating CI/CD pipelines, supporting the other devs creating Dockerfiles, or whatever technology you are using). In other words, type 3, 4, 5 or 6 as per http://web.devopstopologies.com/ . In this case, a sign of shortage is simply too much workload for those two;...


4

The quote is misleading since there is not "a" chef in the kitchen. There are many different chefs, i.e. pantry chef, soup chef, fish chef etc. Wikipedia lists many others. What the quote is thinking of is the "chef de cuisine", which is the overall manager of the kitchen, the CEO if you will. There is also the whole executive hierarchy we know from our IT ...


4

Use a configuration management/automated deployment system. This is what these were designed for. Things like Kubernetes, Puppet, Chef, Ansible and Salt Stack are designed for just this purpose and can be utilized with Golden Master templates, kickstart scripts, Amazon AMIs or just a Docker container. This allows you to use default base templates and then ...


4

IMHO the answer has a lot to do with scale and resource availability. I believe Adam Smith's theory can only be applied at large scale - entire nations/economies in the original context, or, in the SW development context - large development teams. In a large team it is, indeed, more efficient to hire more specialized human resources: they aren't rockstars ...


4

Speaking exclusively from a CI perspective, increasing the number of developers working on a project typically translates into more people working in the same branch. Traditional CI systems have a scalability issue in this respect: the probability of breakages/regressions/blockages increases slowing down the integration speed and inviting smaller teams to ...


4

What I have done (and this is only subjective) is as follows: When a manager thinking about a due date wishes to add people into my team to cut the time needed and seems under MMM, I first discuss with him or her on why this could be bad. My favorite analogy for this is to remind them that if one woman can have a baby in nine months, nine women won't have ...


4

Any business initiative would get a traction if you show its relevance to either topline or bottomline of the organization. Internal initiatives such as devops can only affect the bottomline. You need to identify the costs of recurring work performed by the individiuals and how automation would reduce that expenditure. Even though non-techy managers may ...


4

If you are running your production in docker container it's crucial that those container are being made by the same developers that have build the app running on them. Who else is better place to know what external dependency are needed and so on ... ? Also pipeline can fail at any step during a CD, particularly when it's the docker image build step, ...


4

Here are for example some arguments from a blog post published back 2014 and titled in way quite matching your answer: Much more flexible injection of new technologies into the environment there is still a massive pain point between committing the final tested code and then getting it running on the final production servers. Docker vastly simplifies ...


4

@Abhay Pai why not posting this as 5 different questions? Google for "left shift" in DevOps context. Consider DevOps team patterns http://web.devopstopologies.com/ "While DevOps raise problems and dispatch them to Dev to solve, the SRE approach is to find problems and solve some of them themselves." https://devops.com/sre-vs-devops-false-distinction/ ...


4

start using it if you fail, you can select another technology This approach has two major drawbacks: Technical debt While it may be tempting to apply "fail fast" mentality to architecture and design, skipping or abbreviating the design phase would be a mistake. fast-fail should be used in conjunction with good design practices, not in lieu of them. Making ...


3

My go-to line of reasoning for people who are unfamiliar (or just mistaken) about the term DevOps boils is down to "delivering business value more frequently". This, in my experience, is something very few managers are able to object to. They get it. If they say something like "we just need someone to straighten out our devops, probably just a few weeks of ...


3

I consider myself as a fullstack developer on the basis of the following combination of responsibilities: Front end and back end programming I can do UI changes until some extent: write html, css (as a web developer) and in other hand in some extend provide data to the UI from database, provide it in a service etc. I leave testing, architecture and those ...


3

This question is broad so if my answer is a little off-base feel free to add context and specific examples so that I have a better understanding. Using a machine image such as AWS' AMI would allow you to create a base or golden image, which you could then maintain and distribute or implement in your continuous delivery. Using this architecture you are ...


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