Related Content
 |
Where Do You Start When It Comes to DevOps? DevOps can be a loaded term. Sometimes, you’re just referring to the agile relationship between development and operations. Other people, when discussing it at a conference or in meetings, point toward more frequent releases, to the rate of hundreds of times per day or even per hour. |
|
 |
Overcoming Resistance to Change in Agile Teams For agile software developers, acknowledging that change is inevitable is a core principle in how we work. Yet we often resist change—for a variety of reasons. By understanding human nature and being systematic about how we evaluate decisions, we can give ourselves a way of identifying changes that add value. |
|
 |
The Difference between Plans and Planning As former president Dwight Eisenhower said, "In preparing for battle I have always found that plans are useless, but planning is indispensable." The fact that plans may have to change does not mean planning is a waste of time. In projects, it's always valuable to consider budgeting, resources, and timelines. |
|
 |
3 Ways to Foster Enthusiasm in a Software Team Enthusiasm can’t be forced on you. If you’re not passionate about software, it’s difficult for someone to get you to the point where you wake up in the morning excited to develop a mobile application. However, the conditions of your software team can change your level of enthusiasm drastically. |
|
 |
The Importance of a Dynamic and Open Culture in the Workplace A culture that is carefully built and nurtured in an organization is key to its long term success. While there is no right or wrong answer to which culture should be fostered, a culture that is open and dynamic goes a long way in connecting with employees and fostering a rapport with them. |
|
 |
Shorten Your Feedback Loops to Build Better Software, Faster When we have short feedback loops, we are still in the moment for that feature. We still have the context. The longer the feedback loop, the less likely we are to still have all the context for the feature because we are on to the next piece of work. How long are your feedback loops? Can you shorten them? |
|
 |
Why Chemistry and Character Are Often Afterthoughts When Building Software Teams One aspect of the interviewing process you can’t forget is chemistry. We so often look at someone’s skills and competence in certain areas of the job and completely forget that if that person can’t work well with your current team, development won’t go smoothly. |
|
 |
How Group Norms Enable High-Performing Teams Group norms are the traditions, behavioral standards, and unwritten rules that govern how a team works together. They can be implied or openly acknowledged, but establishing a consistent way the team functions helps the individual members focus less on their own preferences and more on what works best. |
