What is the Agile Manifesto?
We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:
- 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 are the pros and cons of each value listed in the Agile Manifesto?
Individuals and interactions over processes and tools.
Pros: capable people can figure out how to accomplish tasks without a need of process.
Cons: without process productivity gains cannot easily be repeated on future projects.
Working software over comprehensive documentation.
Pros: without the need to document extensively software can be developed more quickly.
Cons: harder for people who did not develop the system to maintain it.
Customer collaboration over contract negotiation.
Pros: can adapt more easily to changing requirements.
Cons: customer representative may not have adequate knowledge of what is needed by their organisation.
Responding to change over following a plan.
Pros: adaptability leads to producing what the customer really wants.
Cons: customer may keep changing the requirements leading to longer delivery time
What are the principles behind the Agile Manifesto?
1. Our highest priority is to satisfy the customer through the early and continuous delivery of valuable software.
2. Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.
3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
4. Business people and developers work together daily throughout the project.
5. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
6. The most efficient and effective method of conveying information to and within a development team is a face-to-face conversation.
7. Working software is the primary measure of progress.
8. Agile processes promote sustainable development. The sponsors, developers and users should be able to maintain a constant pace indefinitely.
9. Continuous attention to technical excellence and good design enhances agility.
10. Simplicity—the art of maximizing the amount of work not done—is essential.
11. The best architectures, requirements and designs emerge from self-organizing teams.
12. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behaviour accordingly.
Release to web manufacture is the correct term. Once you create a pipeline in Jenkins, you need an option to split the pipeline between the web and the warehouse. You need an approval process from a business analyst ie. A product owner.
Role of Product Owner
- To define user requirements.
- To place them in priority.
- Evaluates the issues to define as done.
- Decide if the product is Release to Web or Release to Warehouse.
Traditionally Release to Warehouse has been defined as Release to Manufacture.
The criteria in which the decision is made may include;
- Return in investment for the customer in that they require a rapid return.
- Time to market in that the product has a timely value for particular times of the year.
- Frequency of contact with the customer, while important to give timely feedback to the customer we also have to ensure that we do not annoy the customer with too many updates. Often smaller updates are Released to Warehouse for inclusion with the later Release to Web.
System versions are categorised under 2 major characteristics.
Major Minor Patch
3 .       6 .       1         Jenkins 3.6.1
The other classification is on the build number which may be made from the date and a unique number as multiple Release to Web may happen in any given day.
There may be multiple characteristics of release type with Release to Web ie. Alphabetagramma.
Eg. Eclipse has stable releases and nightly builds.
