Category: Technical Practices

XP Values – The Forgotten Agile Guidance!

| By Mike Hall in Agile, Technical Practices | 0 Comments

When you hear the term “extreme programming”, what do you think of? Coding while skydiving at 15,000 feet? Bug-fixing while scaling the north face of Kilimanjaro? Refactoring while swimming with sharks at the Great Barrier Reef?

For tech nerds like me, we probably think of the wealth of technical practices espoused by this Agile method. These technical practices include stories, pair programming, slack, continuous integration, test-first, and others. Extreme Programing (XP) practices are typically used within a Scrum or Kanban team to help ensure high levels of software quality and continuous integration.

Read More »

Q&A: Allison Pollard Answers Myths, Mobbing, Morals & Craftsmanship

| By Resalin Rago in Agile, Agile Transformation, Technical Practices | 0 Comments

Principal Agile coach Allison Pollard was kind enough to take a break from her busy Keep Austin Agile schedule to discuss how to create a craftsmanship culture, management’s role during a tech turnaround, and the developer secret handshake.

Watch the full video below…full transcript also included.

Read More »

Legacy Code : Deal With It

| By agilevelocity in Agile, Product Development, Technical Practices | 0 Comments

When clients start the journey of an Agile transformation, it is almost never without some pre-existing code. The question immediately comes up of how best to deal with the code developed “before”, as in “before we were doing Agile” or “before we wrote unit test” or “before we were here”. Dealing with legacy code is important because it can be important, even critical, to a business. Its main distinguishing features are that legacy code is feared, changing it can be dangerous, and its continued presence is a drag on development. Read More »

Legacy Applications: Lessons in Coupling

| By Mike Lepine in Agile, Quality, Technical Practices | 0 Comments

I struggled with a number of potential topics for this blog before settling on this one. I understand this isn’t a flashy topic like a comparison of JavaScript MVC frameworks or centralized logging solutions; however, I’ve been working on-and-off with legacy applications throughout my career and have come to truly realize the constrictive nature of coupling logic. Avoiding coupled applications can save your sanity and possibly your business as well. Read More »

Agile Coaching Variations

| By agilevelocity in Agile, Coaching, Leadership, Scrum, Technical Practices | 2 Comments

What is an Agile Coach?

Teams that are adopting or facing challenges with Agile development often turn to an Agile Coach for help. Agile Coaches are usually someone more experienced with Agile process and techniques who can guide the team through rough patches until they can find their own way. Like a sports coach, an Agile Coach may show inexperienced teams how Agile practices work, or may do more listening and asking questions to help the team improve. Traditionally, however, Agile Coaches spend all of their time focused on the coaching role and are not a team member. An alternative variation, the Player-Coach, addresses this limitation. Read More »

Virtualization Makes Me a Better Developer

| By agilevelocity in Technical Practices, Uncategorized | 1 Comment

In the past, developers either had only the choice between multiple machines or sharing development environments. In the first instance, this is an expensive solution and in the second, lots of developers sharing a single environment leads to contention issues. To further exacerbate this problem, the trend is towards application deployments that involve multiple servers. Read More »

An Effective Approach to Agile Development Team Challenges

| By agilevelocity in Agile, Quality, Technical Practices | 0 Comments

A Team’s Agile Development Journey

What typically happens when a software team adopts agile values and principles and implements a framework (such as Scrum)? Normally, after some initial learning, an early positive impact is common along with a feeling of progress. But the team soon encounters new challenges as they realize their journey has only begun. They must now take ownership of their improvement.

Read More »

« Older posts