background preloader

Agile Dev

Facebook Twitter - Sprints Made Simple. Estimates Made Easy. Making Remote Teams Successful With Agile - SerpicoDEV Blog. Posted on December 5th, 2012 Elance recently celebrated its two millionth freelancer. What does this mean for the software development industry? Remote development and design teams are sticking around for the long haul. With access to lower cost talent worldwide at their fingertips, businesses will start incorporating the practice into their long-term strategy.

The recent rise of agile software development raises some questions about implementing it with remote teams. But those who made it work have reaped some major benefits. Good communication just doesn’t happen overnight with remote project teams. Below are some tips that help a remote agile team be more effective. Teamwork Depends on the Agile Team The abundance of low cost talent available remotely doesn’t mean you should just pick the lowest cost team with the best resumes.

Also, take into account the team members enthusiasm and readiness to collaborate. Consider Culture Keep the Daily Scrum (and other open discussions) Software Testing, Monitoring, Developer Tools | SmartBear. Agile Process. Agile Testing. Agility. SCRUM / Agile Development. Agile software development.

Basecamp 3: Manage projects, groups, and client work. 10 Crucial Questions Agile Developers Should Ask Employers. Find out whether that agile development job you're interviewing for might be a nightmare in the making. The demand for agile developers far outweighs the supply. And by far, I mean by light years. Take a look at this infographic that shows how wide the gap is between the available pool of agile developers and the number of job openings for agile. This "agile gap" has significant implications for developers and hiring managers alike. The first implication is this: Most shops looking for agile developers aren't yet agile. They're either just starting out with agile, or they want to be agile, or they say they're agile but really aren't.

If you're a committed agile developer and you're interviewing for a new gig, how can you figure out if the company you are interviewing with is full of hot air or really is an agile shop? The truth is that there's no such thing as a perfect agile shop, because the industry is decades away from full maturity. . [ Looking for a promotion? 1. 2. 3. 4. 5. 1 of 2. The Art of Agile. Adopting Agile An Extreme Stake in the Ground - 21 Aug, 2005 A fresh look at XP, sans humility, maturity, and wisdom.

Change Your Organization: A Diary - 10 Mar, 2006 Six months of changing an organization from within. It's the Software, Stupid! - 21 Oct, 2007 We keep forgetting that we're here to develop software. Scrum and XP Practices: Cross Reference - 13 Dec 2007 A comparison of Scrum, both editions of XP, and The Art of Agile Development. Shu-Ha-Ri and The Art of Agile - 2 Jan, 2008 In order to do agile development your way, you have to do it some way first. Opinionated and Antisocial - 16 Jan, 2008 The right method for your team is customized to the needs of your team. Your Brain on Agile - 6 Feb, 2008 A story cut from The Art of Agile Development.

Practices or Principles? What's more important, using agile practices or understanding agile principles and values? Marick's Missing Manifesto - 20 Feb, 2008 Real success takes real work. Should We Adopt Scrum or XP? Cargo Cult Agile - 14 May, 2008. Scrum and XP Practices: Cross Reference. Home → Blog → Scrum-XP-Practices-Cross-Reference Let's Code: Test-Driven JavaScript, my new screencast series on rigorous, professional JavaScript development, is now available!

Check out the demo video here. Print by James Shore 13 Dec, 2007 I've had several people tell me how useful the Scrum/XP cross-reference in our book is, so I thought I'd share it with you, too. To create this chart, I referred to Ken Schwaber & Mike Beedle's Agile Software Development with Scrum and both editions of Kent Beck's Extreme Programming Explained.

If a row lists n/a for a particular method, that means that there is no corresponding practice defined in that method. If you have corrections, please let me know, with references when possible. Home → Blog | Permanent Link. Differences Between Scrum and Extreme Programming. Scrum and Extreme Programming (XP) are definitely very aligned. In fact, if you walked in on a team doing one of these processes you might have hard time quickly deciding whether you had walked in on a Scrum team or an XP team. The differences are often quite subtle, but they are important. I think there are four main differences between Scrum and XP: Scrum teams typically work in iterations (called sprints) that are from two weeks to one month long. XP teams typically work in iterations that are one or two weeks long. Scrum teams do not allow changes into their sprints. These are small and often subtle differences between Scrum and XP. Untitled. NEWS (June 2015): 2nd edition available!

Read the online version at InfoQ, or purchase a print version from there. “Your writing style is great, and the information that you provide is very useful … Your are an asset to the Scrum community” — Ken Schwaber (co-founder of Scrum) “Henrik’s book is a starter kit of basic practices that help teams move beyond trying to do Scrum to executing Scrum well.” — Jeff Sutherland (co-founder of Scrum) “Henrik’s book isn’t a philosophical explanation of why Scrum works or why you might want to try this or that. It is a description of how one well-running agile team works. Henrik provides a host of good practices along with the necessary context to help us learn better how to do Scrum and XP in the trenches of our own projects.” — Mike Cohn (author of Agile Estimating and Planning) “a great contribution to the body of Agile knowledge, and a fun read” — “Of all the Agile articles and books that I’ve read (and even those that I’ve written.

Continuous Integration. I vividly remember one of my first sightings of a large software project. I was taking a summer internship at a large English electronics company. My manager, part of the QA group, gave me a tour of a site and we entered a huge depressing warehouse stacked full with cubes. I was told that this project had been in development for a couple of years and was currently integrating, and had been integrating for several months. My guide told me that nobody really knew how long it would take to finish integrating. From this I learned a common story of software projects: integration is a long and unpredictable process. But this needn't be the way.

This contrast isn't the result of an expensive and complex tool. When I've described this practice to people, I commonly find two reactions: "it can't work (here)" and "doing it won't make much difference". The term 'Continuous Integration' originated with the Extreme Programming development process, as one of its original twelve practices. Agile - Scrum and Extreme Programming (XP) : Best Practices. Books | Kanban Library | Lean & Kanban Resources. Here you will find a rich collection of books on Kanban and process management that cover a wide variety of subjects, written by prominent authors only.

The content within these books is definitely worth a read. Kanban: Successful Evolutionary Change Number of pages: 278Publisher: Blue Hole PressPublication date: April 2010 Kanban has become a popular way to visualize and limit work-in-progress in software development and information technology work. Teams around the world are adding Kanban around their existing processes to catalyse cultural change and deliver better business agility. This book answers the questions: What is Kanban? Why would I want to use Kanban? Personal Kanban: Mapping Work - Navigating Life Number of pages: 216Publisher: CreateSpacePublication date: February 2011 Personal Kanban takes the same Lean principles from manufacturing that led the Japanese auto industry to become a global leader in quality - and applies them to individual and team work. The Lean Startup. Small team scrum and kanban. Roles on Agile Teams: From Small to Large Teams. There are several key differences between the agile approach to team organization and the traditional approach.

Agile teams are "whole teams". Whole team is an Extreme Programming (XP) practice that advises you to have sufficient skills within the team itself to get the job done. The implication is that the development team has the requisite testing skills, database skills, user interface skills, and so on and does not rely on external experts or teams of experts for these sorts of things. Agile teams are formed (mostly) of generalizing specialists. A generalizing specialist, sometimes called a craftsperson, is someone who has one or more technical specialties (e.g. Small Agile Teams There are several roles, which have different names depending on the methodology being followed, common to agile teams.

Team lead. Figure 1 overviews the structure of a small agile team. Technical experts. Figure 1. Figure 2. Large Agile Teams Project management activities. Figure 3. Suggested Reading. What President Eisenhower Can Teach us About Prioritization. President Dwight D. Eisenhower stayed extremely busy as the 34th U.S. President, both commanding the Allied Forces during WWII and managing his duties as a decorated five-star general. It takes impressive organizational skills to succeed at just one of these positions, not to mention all three. Wondering how he did it? The Eisenhower Method To stay on top of things, Eisenhower quickly determined what needed to be done first and focused on those items which he deemed most pressing. Critical and Do Now: Of high importance, and time sensitive.Critical, but Do Later: Critical for me to do personally, but okay to set a further end date for completion.Not Critical, but Do Now: Delegate to someone who can get it done now.Not Critical and Do Later: Let go of these; they’re time wasters.

“Critical” and “Do Now” So what’s the difference between Critical and Do Now? Is There an App for That? You don’t have to be a five-star general to think like one. Best to do list app for Windows, iOS. Plan differently | Appfluence. Manifesto for Agile Software Development. 9 agile development tools for working at warp speed. Dapulse’s project management tool enables teams to track the status of their high-level goals while offering fine-grained management capabilities that makes project collaboration faster.

While Dapulse can be used in software development, Australia-based Rescon Builders uses it to manage construction projects. “We use Dapulse as a task management, project planning, and company portal,” Rescon’s Timothy Cocaro says. “Having different boards, we can easily create tasks that are department-specific, e.g., ‘administration,’ ‘construction,’ etc.”

Rescon has been using Dapulse for the past two years to track the overall status of projects and approvals for its granny flat construction projects. “Given the application is so visual and easy to understand, it acts as our company portal. All our staff can easily view, contribute, and comment on those boards they have access too,” Cocaro says. ZenHub - Project Management for Agile Teams in GitHub. Thank you for signing up for YouTrack Incloud!