develpreneur podcast
Posted on The Agile Manifesto

Work Together To Be An Agile Team

The principle we cover in this episode is short but powerful.  It is also one that goes to the heart of defining an Agile team.  We do not focus on the technical staff and developers.  There also needs to be an inclusion of the business people.  Therefore, development in a vacuum is not valid.  Regular communication with the customer or their representatives is essential. Business people and developers must work together daily throughout the project. The Agile Team Software development has progressed to where subject matter experts and business analysts are a typical piece of the puzzle.  That has not always been the case.  Thus, it is worth looking at how defining the team as we do today is beneficial... Read more

aws developer tools
Posted on Python-Django Crash Course

AWS Developer Tools – An Overview

Our series of tutorials on Python-Django will include the use of several AWS Developer tools.  Therefore, we want to take a look at those from a high-level before we get very far in the material.  This presentation skims over the ones we will be using, along with a few that may prove useful in your projects.  None of these services are required for this series, nor do you need to follow up with other episodes to get an understanding of these tools.  However, we will be showing some examples as the series progresses. A Quick Tour Amazon provides some excellent tutorials for each of their services.  This presentation tries to take those highlights a little deeper.  We look at the... Read more

develpreneur podcast
Posted on The Agile Manifesto

Deliver Working Software Frequently – Clear and Open Communication

The third principle of the Agile Manifesto tells us to deliver working software frequently.  This step is an essential factor in satisfying the customer.  While we want to avoid the “are we there yet?” approach to delivering a solution, incremental is valuable.  When we take this principle to heart, we provide confidence in our progress, along with opportunities for feedback.  Therefore, we need to look at this closer for small and large applications. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. Deliver Working Software Frequently These four words are sometimes easier said than done.  The implementation phase is dynamic by definition.  We should be steadily making changes... Read more

develpreneur podcast
Posted on The Agile Manifesto

Changing Requirements – Welcome Them For Competitive Advantage

In this episode, we continue a walk through the twelve principles of the Agile Manifesto.  The second principle focuses on change and how it can be a competitive advantage.  Changing requirements can be a headache and cause slippage.  However, adapting to them can be a game-changer. Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage. Satisfy The Customer I want to start the discussion about changing requirements with a call-back to our first principle.  Our primary focus is on satisfying the customer.  Therefore changing requirements signal a change in what is needed to satisfy them.  We may find these alterations frustrating and might even experience over-runs based on them.  Nevertheless, we must adapt... Read more

develpreneur podcast
Posted on The Agile Manifesto

Satisfy The Customer – The Agile Manifesto

We start our focus on the Agile Manifesto with a deep dive into the twelve principles they address.  Thus, we begin at the first principle and will focus on that one in this episode.  This point also gives us a foundation of trying to satisfy the customer. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. Satisfy The Customer Anyone that tells you Agile is primarily about anything other than the customer is misinformed.  The first item states that the highest priority is the customer.  Not only that but satisfying them.  Therefore, we are not focused on meeting requirements or even an incredible design.  Customer satisfaction is number one.  Many things go into... Read more

python-django
Posted on Python-Django Crash Course

Python-Django: A Crash Course Introduction

Python-Django is a combination for web development that is growing at a rapid pace.  There are also new services being added to the AWS list on an almost daily basis.  When you combine these two facts, it makes sense to spend time on a crash course that will get us up to speed on these platforms.  We start this series with a high-level look at Python and Django. Python-Django in Under 60 Minutes The bulk of this tutorial highlights how to get started with this combination as we leave the AWS focus for a future presentation.  When you are done with this you should be able to get the basics of a hello world created in Python and Django.  However,... Read more