Vocab and Agile Notes

toc: true layout: post description: Vocab to learn categories: [markdown] title: Vocab and Agile Notes

Vocab Definition
Vocab Explanation
Sequence More than one line of code
Static Text Text that doesn’t change
Input Code that is inserted by the user
Output The response the computer generates from the input
Scrum Master Manage scrum board and ensure agile framework is followed track issues and looks for opportunities for team to improve
DevOps Combination of cultural philosophies, practices, and tools that increase a team’s ability to deliver applications and services at high velocity
Frontend Developer Develops what users interact with and what the user sees
Backend Developer Develops what goes on behind the scenes, what the user doesn’t see, the technical stuff
J.son Transport information between systems
Agile Practices like pair programming, planning sessions, sprints…
Sequence Two or more lines of code
Array Stores collection of multiple items under single variable name

Agile Notes 1.Our highest priority is to satisfy the customer through 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 must 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 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 behavior accordingly.