RazTechPro gist felülvizsgálása . Revízióhoz ugrás
1 file changed, 0 insertions, 0 deletions
IntroToAgileAtZipcode fájl átnevezve erre: IntroToAgileAtZipcode.md
Fájl átnevezve változtatások nélkül
RazTechPro gist felülvizsgálása . Revízióhoz ugrás
Nincsenek változtatások
RazTechPro gist felülvizsgálása . Revízióhoz ugrás
1 file changed, 1 insertion, 1 deletion
IntroToAgileAtZipcode
| @@ -5,7 +5,7 @@ | |||
| 5 | 5 | ||
| 6 | 6 | #### The focus is on the engineers doing the work and the manner in which they work together to deliver working software. | |
| 7 | 7 | ||
| 8 | - | #### At Zipcode Wilmington, Agile is the marriage of ProDev and Technical. | |
| 8 | + | #### At Zipcode Wilmington, Agile is the marriage of ProDev and Java/Data programs. | |
| 9 | 9 | ||
| 10 | 10 | ||
| 11 | 11 | ## Successful Technical Teams | |
RazTechPro gist felülvizsgálása . Revízióhoz ugrás
1 file changed, 59 insertions
IntroToAgileAtZipcode(fájl létrehozva)
| @@ -0,0 +1,59 @@ | |||
| 1 | + | # Introduction to Agile at Zipcode Wilmington | |
| 2 | + | ## What is Agile? | |
| 3 | + | ||
| 4 | + | #### Agile software development is an umbrella term for a set of frameworks and practices based on the values and principles expressed in the Manifesto for Agile Software Development. | |
| 5 | + | ||
| 6 | + | #### The focus is on the engineers doing the work and the manner in which they work together to deliver working software. | |
| 7 | + | ||
| 8 | + | #### At Zipcode Wilmington, Agile is the marriage of ProDev and Technical. | |
| 9 | + | ||
| 10 | + | ||
| 11 | + | ## Successful Technical Teams | |
| 12 | + | ||
| 13 | + | #### Technical teams at Zipcode Wilmington, as well as in the greater software engineering industry, are made up of engineers who work together to deliver a working software product. | |
| 14 | + | ||
| 15 | + | #### At Zipcode Wilmington, the software product may be a lab, a project, or an application. | |
| 16 | + | ||
| 17 | + | #### Each team member on an Agile team is an owner of the work the team is doing. Each team member is responsible to other team members. So, it is crucial that engineers conduct themselves with professionalism and humility. | |
| 18 | + | ||
| 19 | + | #### Some Agile team characteristics we will practice: | |
| 20 | + | ||
| 21 | + | + Every team member contributes their talents | |
| 22 | + | + No individual talent makes a team member a better leader | |
| 23 | + | + No individual talent makes a team member’s opinion more important | |
| 24 | + | + Every team member is responsible for leading the team | |
| 25 | + | + No team member cedes their leadership responsibilities to another team member | |
| 26 | + | ||
| 27 | + | ||
| 28 | + | ## Agile Manifesto | |
| 29 | + | ||
| 30 | + | #### Look online for the Agile Manifesto. This is the software engineers' creed. | |
| 31 | + | ||
| 32 | + | #### In shorthand, the manifesto tenets are: | |
| 33 | + | ||
| 34 | + | + Continuously deliver what is asked for | |
| 35 | + | + Welcome change; be flexible; be agile! | |
| 36 | + | + Deliver working software frequently in sprints or cycles | |
| 37 | + | + Daily standups; engineers and stakeholders are on the same team | |
| 38 | + | + Every team member is an owner and a leader; lift each other! | |
| 39 | + | + Face-to-face communication; set policies together; don’t hide behind emails and texts when you need to discuss things | |
| 40 | + | + Working software is imperative; committed code compiles | |
| 41 | + | + No one is idle; team maintains a sustainable pace | |
| 42 | + | + Commit to technical excellence and design: UML, task breakout, planning, Git best practices, paired programming | |
| 43 | + | + Keep it simple; break out tasks; remove waste | |
| 44 | + | + Self-organizing teams; every voice is used and heard | |
| 45 | + | + At regular intervals, do a retrospective | |
| 46 | + | ||
| 47 | + | ## Engineering Agile Practices | |
| 48 | + | #### There are many practices software engineers use in the industry. At Zipcode Wilmington, there is a subset of those practices you will use during the program: | |
| 49 | + | ||
| 50 | + | + Set and abide by policies | |
| 51 | + | + Daily Standups - Three questions (plus a battery check) | |
| 52 | + | + Brainstorm, design, plan, do task breakout together as a team | |
| 53 | + | + Use a Kanban board (see Projects in Github) | |
| 54 | + | + Remove blockers with urgency and commitment | |
| 55 | + | + Do retrospectives - Three questions | |
| 56 | + | ||
| 57 | + | ## Cohorting | |
| 58 | + | ||
| 59 | + | #### Cohorting is being a good teammate. It's listening. It's wanting your teammate to be successful. It's making your teammate excel. It's what Agile is all about. | |