W3Nuts is adopting the Agile SCRUM framework. This is a process that will take time to develop and we aspire to release our services into the wild of the computing world on the 17th of October 2017. We will do this by writing 500 word daily journal of our findings along this journey.
Today, we are starting to learn about Agile. Now Agile is a value based algorithm that differs from a traditional planning computer development environment. The major difference is that Agile deliverers results in weeks not months. It relies on a small team and is constantly evolving. It stands on a 12 point principle that includes a rapid development/deployment, a need for face to face interface and simplicity.
We note that there is a SCRUM Project Management course in Edinburgh in September that would be a good idea to attend and it cost £1k (https://nkdagility.com/training/sheduled/professional-scrum-master-edinburgh-september-2017/?gclid=Cj0KEQjwnazLBRDxrdGMx-Km4oQBEiQAQJ1q69Rz9hFVsOYJNwY4_D0pSWCu5PVFoNUIsX942UBBYPMaAjap8P8HAQ). It requires a good understanding of Scrum a Pocket Guide that will be incorporated into this blog.
There is a major conversation being had around Agile with regards to documentation. Scott Amber suggests that documentation should be JBGE (Just Be Good Enough). Alistair Cockburn goes on to offer that documentation needs to be good for the next win in the next game. There is a general movement within Agile to move away from heavy documenting code.
Agile has over a dozen frameworks. Each are tailor suited for different needs. The main types of frameworks include Practical (XP, Pragmatic, Modeling) Work Flow/Adaptive (Scrum and Kaban) and specific (FDD).
An adaptive framework uses humans to design systems for specific situation and response to these situation in a live dynamic environment. Most of the frameworks within Adapt fit well within this type of tailoring environment. While SCRUM is a adaptive method, it is not prescriptive. It is more of a road map giving a set of guidelines recognizing that the SCRUM framework is not perfect but able to be enhanced through time.
Historically, Adaptive was seen as only being suitable for non critiacl product development. Now they have R-Scrum and Safe Scrum that I suitable for industries like medical and financial.
The software development is object-oriented using languages like Small Talk, LIPS and JAVA.
There are some concerns over traditional waterfall practices. Some claim that the lack of design may cause considerable re-work. However, Agile is an iterative process. It is important to focus on stories with specific goals. If there is additional information that is associated with the story, it may be needed to create a new story and re evaluated the priority of the overall project.
Agile is well suited for grassroots projects that are highly evolving. Some feel that this can be a constraint with respect to long term funding and designers can fail to understand the need for continuous training and development.
There are different roles that are needed within the Adaptive structure. It is important to have a product owner that gives a customer centric view to the project. The scrum master must not be a contributor nor a developer but a facilitator who removes project barriers.