What gets measured, gets managed.
Peter Drucker, “The Practice of Management”, 1954
In his book “Up the Organization”, Robert Townsend gives 10 evaluation criteria that you can use to rate your boss as a leader.
Here is, in a nutshell, the difference between a boss and a leader: a boss is someone who was appointed by the organization to manage a team. A leader, on the other hand, is someone in the organization who inspires people. A boss pushes people to work, a leader pulls them towards his vision. Some bosses are leaders, others are just managers. For a brief comparison between (bad) boss and leader characteristics, you may refer to the info-graphic at the end of this post.
Back to Townsend’s criteria, the author suggests that you score each of the following characteristics from 0 to 10, the total (from 0 to 100) is you boss’s rating. How much is your boss : Continue reading “Is your Boss a Leader ?”
The digital technology industry has been moving in a very fast pace over the last decades. Companies that are unable to adapt have been left behind (Nokia, Kodak, etc.). Agility is a key skill for a company to remain competitive.
Since the Agile Manifesto for software development, declared in 2001, several software companies have been moving towards this mindset. Some companies went further, and adopted Agile way of development in industries other than software industry.
If your time to you is worth saving
Then you better start swimming, or you’ll sink like a stone
For the times they are a-changing.
Is it possible for any company to apply Agile ? How about big companies, with complex organizations, top-down policies, rigid processes, over-specialized teams, and other bureaucratic burdens ? And above all, what is Agile and what is not Agile ? First, let’s review the life-cycle of a product.
A product life-cycle can be broadly divided into 4 phases as shown on the figure below:
Software development is a tough process. It starts off by identifying and understanding what the user/client needs, and ends by deploying a solution that may, or may not, satisfy the user. During this journey, a group of Homo sapiens work together, organize teams, conceive plans, define tasks, rules and tools. They spend time and effort specifying, designing, programming, testing, documenting, bug fixing, etc. and hoping that they will deliver on time.
Some of those sapiens groups outperform their peers, and manage to provide high quality solutions on time. Other groups fail to deliver any solution, and waste their effort, time and resources in vain. Successful software developers (at least some of them) decided to help the others with their skills, by teaching them how they are doing Software development. This is why, on February 11th – 13th, 2001, at The Lodge at Snowbird ski resort in the Wasatch mountains of Utah, USA, seventeen Homo sapiens met to talk, ski, relax, and try to find common ground—and of course, to eat. What emerged was the Agile Software Development Manifesto.
Agile is a Software development mindset that embraces change. It is neither a process nor a model, but rather a set of values and principles. It is a flexible approach for Software development, that helps organizations to adapt fast to the market change.
Processes and documentation are important, but not the main concern in Agile mindset.
There exist a wide variety of software development models, that have evolved to address the evolving challenges facing the software industry. In this post, the following models are reviewed:
- Waterfall Model
- Sashimi Model
- Incremental Model
- Unified Process Model
- Spiral Model
We present a summary of their pros and cos, and the cases for which each model is best suited for. Note that the same models apply to other product (or system) development, therefore, we will use software and product interchangeably in this post. It is worth noting also that, in practice, most organizations combine two or more models in their development process.
First, let’s take a look at the software development phases.
Software Development Phases
The conventional way to conduct software development projects consists broadly of the following steps:
- Requirements: they are gathered from the customer/user at the beginning of the project. Requirements are system-level and independent of the technical solution.
- Architecture & Design: architecture deals with the high level design, and the definition of the interfaces and interactions between subsystems. Then detailed design deals with components, functions, subsystems, etc.
- Implementation: the design is now a coded software that is ready to be tested.
- Testing: it includes verification and validation (V&V) of the product. First, the verification means to check that what we designed is working as expected (unit testing for instance). Then the validation is to check that what we designed and implemented actually fulfills the requirements (system testing).
- Release: the software is released and is ready for deployment. Sometimes, deployment and maintenance are considered to be part of the software development phases.
This sequential process is called Waterfall, as it can be illustrated in the figure above. Continue reading “Software Development Models”