↓ Skip to main content

Agile

MVP – Minimum Viable Product

MVP – Minimum Viable Product

·1 min
“The minimum viable product is that product which has just those features (and no more) that allows you to ship a product that resonates with early adoptors; some of whom will pay you money or give you feedback” – Eric Ries
DONE – when done means DONE

DONE – when done means DONE

·1 min
When is something done? What does DONE mean? In the teams of software development, here is a definition that can apply to this process: Definition of Done The meaning of done is an agreed upon list of the activities necessary to get product increment to a production ready state.
Story pointing

Story pointing

·3 mins
Procedure & Rules An important element of Scrum is to estimate the complexity of features in the product backlog. For the estimation process, we use a simplified Fibonacci sequence: 0, 1, 2, 3, 5, 8, 13, 20, 40, 100.
Development Process Flow

Development Process Flow

·2 mins
Your software team has a process that use to complete work. Normalizing that process–i.e., establishing it as a workflow–makes it structured and repeatable, which, in turn, makes it scalable. With your development team, you can take an iterative approach to workflow management because it helps you meet your goals faster and exemplifies your team culture.

A web-developer’s guide to help eliminate non-coding tasks and get code done faster

·1 min
Microsoft have just published this great eBook which helps web developers cut right to the code scripting of environments to make all the firewall ports and get code done quickly by providing an overview of key services in the cloud, what services to use based on your needs, step by step guidance, sample code, sample applications, and a free account to get started.
Differences between Scrum and Kanban

Differences between Scrum and Kanban

·6 mins
Scrum and Kanban are two terms that are often (incorrectly) used interchangeably or thought to be two sides of the same coin. In reality, there are significant differences between these two Agile methodologies. Understanding these differences is key to choosing the path that will work best for your environment. In a nutshell, what is Scrum? Without getting too detailed, Scrum is a tool used to organise work into small, manageable pieces that can be completed by a cross-functional team within a prescribed time period (called a sprint, generally 2-4 weeks long). To plan, organise, administer, and optimise this process, Scrum relies on at least three prescribed roles: the Product Owner (responsible for initial planning, prioritising, and communication with the rest of the company), the Scrum Master (responsible for overseeing the process during each sprint), and the Team Members (responsible to carry out the purpose of each sprint, such as producing software code.) Another common tool used by scrum teams is the Scrum Board – a visual representation of the work flow, broken down into manageable chunks called “stories”, with each story moved along the board from the “backlog” (the to-do list), into work-in-progress (WIP), and on to completion.

Managing Sprints in a Scrum

·1 min
There are many ways of managing a Scrum Sprint, but I always look for the easy ways, I came across Deborah Hartmann, spreadsheet which I have found very useful and easy to get along with. Once you understand the processes of Scrum and what is required the spreadsheet speak a thousand words.