[Recommended Reading] Principles behind the Agile Manifesto

Source: Principles behind the Agile Manifesto

We follow these principles:

Our highest priority is to satisfy the customer
through early and continuous delivery
of valuable software.

Welcome changing requirements, even late in
development. Agile processes harness change for
the customer’s competitive advantage.

Deliver working software frequently, from a
couple of weeks to a couple of months, with a
preference to the shorter timescale.

Business people and developers must work
together daily throughout the project.

Build projects around motivated individuals.
Give them the environment and support they need,
and trust them to get the job done.

The most efficient and effective method of
conveying information to and within a development
team is face-to-face conversation.

Working software is the primary measure of progress.

Agile processes promote sustainable development.
The sponsors, developers, and users should be able
to maintain a constant pace indefinitely.

Continuous attention to technical excellence
and good design enhances agility.

Simplicity–the art of maximizing the amount
of work not done–is essential.

The best architectures, requirements, and designs
emerge from self-organizing teams.

At regular intervals, the team reflects on how
to become more effective, then tunes and adjusts
its behavior accordingly.”

Advertisements

Leave a comment

Filed under Articles, General, Management, Recommendations

[Recommended Reading] Little’s Law

Source: Little’s Law Wikipedia

“In queueing theory, a discipline within the mathematical theory of probabilityLittle’s resulttheoremlemmalaw, or formula is a theorem by John Little which states that the long-term average number L of customers in a stationary system is equal to the long-term average effective arrival rate λ multiplied by the average time W that a customer spends in the system. ” Read more…

Image Source.

Leave a comment

Filed under General, Recommendations

[Recommended Reading] KanBan

Source: KanBan Wikipedia

“Kanban (看板) is a scheduling system for lean manufacturing and just-in-time manufacturing (JIT). Taiichi Ohno, an industrial engineer at Toyota, developed kanban to improve manufacturing efficiency. Kanban is one method to achieve JIT. The system takes its name from the cards that track production within a factory. For many in the automotive sector Kanban is known as “Toyota name plate system” and as such some other auto makers won’t use the term Kanban.”Read more…

Image source.

Leave a comment

Filed under Articles, Recommendations

[Recommended Reading] Pair Programming

Source: Pair Programming Wikipedia

“Pair programming is an agile software development technique in which two programmers work together at one workstation. One, the driver, writes code while the other, the observer or navigator,[1] reviews each line of code as it is typed in. The two programmers switch roles frequently.” Read more…

Image Source.

Leave a comment

Filed under Articles, Recommendations

[Recommended Reading] Machine Learning

Source: Machine Learning Wikipedia

“Machine learning is a field of computer science that gives computers the ability to learn without being explicitly programmed.[1]  Read More…

Image source.

Leave a comment

Filed under Articles, General, Recommendations