Altama Software Systems Inc

Process

It's time for a change.

How we do things differently

 

ProcesS Assembly

Let's start assembling the project


AgilitY Assembly

Plan for changes within the project


Usability Assembly

How will people use this solution?



Process 

Let's create the project


Agility 

Create processes to support change


Usability

Test how the solution is used



Process ++

Let's improve the project


Agility ++

Incorporate frequent improvements


Usability ++

Communicate how to improve its use


 

What is Agile?

Agile is a group of solutions expressed through processes and methods that extend the "Kaizen" approach to project management. Agile was devised in 2003 when a group of engineers constructed the Agile Manifesto.

 

It says this:

Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan

That is, while there is value in the items on
the right, we value the items on the left more.

What is Scrum?

Scrum is a framework of Agile, of which has been engineered carefully to involve highly functional teams.

This Agile system provides development teams a set of rules in order to operate efficiently as a team. These rules are designed around communication processes, and empower a controlled method to communicate between business teams, and production teams.

 

Certain rules include:

Daily 15-minute stand-up meetings
Timed planning, and retrospective meetings
Defined goals and outcomes of meetings
A mathematical solution to determining priority

What is XP?

XP or Extreme Programming is another framework of Agile that has been engineered to produce defect-free code.

XP can get very technical; however it pairs very well with Scrum since Scrum is devoid of technology processes, and XP does not clearly define communication standards.

Extreme Programming is guided by the teachings of Agile, but involves strict processes in software development. Some of these processes include the importance of test-driven development or TDD.

 

Test Driven Development:

TDD is a way of building software that involves creating tests for business requirements before writing functional code. Testing business logic before anything is created increases the "future-proof" ability in software. Test-driven development is a cost-reduction method to add new functionality and to perform maintenance in less time. 


 

Why does any of this matter?

Projects frequently fail due to a lack of planning and the mis-management of executed plans. When you choose to work with Altama, you are choosing a competent team who recognizes failures within a project, and has established processes to avoid them. 

We build with Agile because it has been proven to increase quality of projects, decrease costs, and decrease stress between customers and staff.

 

The Agile Manifesto

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.

For more information, here's a link to Wikipedia (Agile)