One side of my news feed showcases how we are innovating with technology in so many new ways, and the other side just tells how screwed we are. Which is it? Are we innovating or are we drowning in big problems?
In this post we will explain how we can move to shared responsibility by focusing away from roles in Scrum.
Code metrics are a conversation starter. Metrics are a great way to start the conversation that says, “Hey, I notice there may be a problem here, what’s up?” In this post, I’ll go through a few cases where I’ve used metrics effectively in concrete ways. This is personal; each case is different and your conversations will vary.
To fully realize predictability, progress visibility and collaboration through Agile, you need separate Agile systems to manage responsibilities and accountabilities that are different for each role.
Described by Elisabeth Hendrickson as originating with the misguided belief that “testers test, programmers code, and the separation of the two disciplines is important“, the traditional segregation of development and testing into separate phases has disastrous consequences for product quality.
One bad habit that permeates the industry is fellow developers arguing about how code is written. Although their hearts are in the right place, in most cases their focus may need adjustment. The late author Zig Ziglar was known to say "Be firm on principle but flexible on method." This is an excellent approach not only to life but programming.
Iwas amazed by an interesting feature of git, that it allows you to edit and change previous commit messages.
Counteroffers are a fairly common occurrence in technology and other competitive job markets, and much of what we think we know about counteroffers seems to originate from agency recruiters.
Github’s pull requests are a terrific tool for collaborating on open-source projects. I get one or two a week on average for my projects, and I love it. The UI is very clean – you get to see exactly the changes, the full branch if you’d like, even the Travis CI integration is working checking that the branch still passes your tests.
What do you do if you find a problem in your code base but can’t fix it right now? If you are like many developers you probably put something like a todo comment next to it, so you don’t forget it.
Most folks have heard the old adage that you never discuss religion or politics in polite company. Frankly, I’m guilty of both because I think it’s fun and I can take it. As a society, I think it’s time to consider a third category of zealotry that needs to be banned from our fancy dinner parties… agile methodology.
Ditch the job ladders and formal roles. Pay everyone in the company the same base salary. For each of the skills an individual can display and utilize, increase their pay by a set, published amount. I've had this in my head for years. This is the first I've put it to paper. It's not fully formed and I've never tried it. This is a concept. I suspect it is wrought with issues, but I know for certain that job ladders are wrought with issues.
Git makes branching a commodity and each feature can be developed in a separate branch. This is desirable since the merging process may be out of your control. If you develop on the default master default branch and a given committed feature is postponed, you will have to revert your changes prior to starting working on a completely different feature.
The core question, which will continue recurring, is: can you truly understand Agile, or any development methodology, without having done that most fundamental development work: programming?
New agile "teams" are often just people who bear some sort of relation to the work that needs to be done. In this article we look at how rigor can be drawn around team boundaries, and at the duties stakeholders must fulfil in a new agile way of working.
Before we start our conversation about governance in the structure-governance-metrics framework we’re building out, I want to take a minute and see if I can finally tell you guys about the house my wife and I were planning to build this past summer.
I thought we’d grown out of Scrum, I admit to describing it as agile training wheels, but I’ve found a new love for it and its constraints. I’m glad I got a taste of what happens when you remove them, and perhaps there are organisations that will flourish when you do. But I wonder if there really is?
Sometimes, you don’t have short projects, so projects get backed up, and your managers ask you to work on several things at once. Or, the managers can’t decide which project is #1. Somehow, you end up doing several things “at once.” This is the multitasking problem, and this is the cost of delay in this part.
There are many ways for a business to release software. Two common approaches are projects and products. They sound similar but are vastly different.
Being a long timer in the Collaboration (dare I say cooperation) software industry, I regularly get requests to provide a “Total Cost of Ownership” analysis so that clients can compare one vendor against another. So, in 2014, what is the REAL cost of email?
Finding and keeping good programmers is a challenge for any business. Salary and promotion opportunities aside, sometimes it's the small things that add up. Putting defection aside, happy programmers code faster and produce less bugs. What are those little things?
Well, it seems that in many organizations we’ve got some things to figure out before we can even really think about doing Scrum. First, we need to figure out what kinds of teams we are planning to form and how we are going to go about forming them.
It’s getting all too common to walk into an organization that thinks they are doing Scrum, but isn’t seeing any real benefit. They’ll think they’re doing Scrum because everyone attends a daily standup, they plan every two weeks, and so on. They know the ceremonies. They know the roles. But something isn’t working.
Are you looking for the best Agile Methodology PPTs? We have scoured the web to pull together a list of the greatest Agile Methodology PPTs we could find. We hope you find these helpfully whether you are just starting your Agile journey or are well on your way and just looking for ways to improve.
At times life can feel like one constant distraction in a room filled with interruptions. Add the extra dimensions of new technologies, constant growth, continual communication, and never-ending deadlines brought on by software development, and a general sense of being overwhelmed or confused is understandable