sertmer

Accountability Group DTR

Template

Group Members: John T., Allison W., Raisa P., Scott E.

Schedule for weekly meetings and regular Stand Ups (must have 1 weekly meeting and at least 2 Stand Ups a week): Be prepared to come up with 2-3 different times in case groups overlap so that Tracey can meet with all groups.

1 weekly meeting:

sertmer

Group Member Names:

• Colin Koga, Zac Isaacson, John Travers, Scott Ertmer, Austen Dunn

Goals and Expectations for the Project (You don't know the details of the project yet. But as you go into any project, how do YOU define success?)

• Colin Koga: learning new lang (native) and solid testing, and D3.
• Zac Isaacson: Learning django/ flask is a priority. New lang's and frameworks.
• John Travers: Getting more comforatble with python, new frameworks and langs
• Scott Ertmer: React native, working with D3 for some visual magick
• Austen Dunn:

sertmer

Group Member Names:

• James Miller and Scott Ertmer

Goals and Expectations for the Project (You don't know the details of the project yet. But as you go into any project, how do YOU define success?)

• Scott: Progress over past abilities
• James: I would like to better solidify my knowledge of the backend side of things, while also maintaining/improving my skills in TDD, Git Workflow, refactoring, etc. I think we will know that we were successful if we feel we did that the best of our abilities and feel good about meeting all the requirements of the project. If possible we may want to try and incorporate cool graphical libraries like Three JS and D5 (?).

Team strengths & collaboration styles (consider discussing your Pairin qualities here):

• Scott: Direct and quick to discuss pros and cons.

sertmer

Template for DTR Memo

Group Member Names:

• Vee Andrade
• Scott Ertmer
• Ben Firth

What feedback did you get on FitLit today? What was your biggest takeaway?

• Vee Andrade: params and more dynamic functions, taking initiative to try to fill your gaps.
• Scott Ertmer: Refactoring functions using params to make them more dynamic, Choosing what not to show to the user

sertmer

Who am I?

• I am someone dedicated to growth - growth of myself, and those around me. I have a background in the visual arts, but I never wanted to be an artist, hanging work in galleries. From the beginning, I always saw myself as a helper, leader, or safety net. I taught visual arts for 7 years, and throughout those 7 years I helped others grow, and grew a lot myself as an artist, teacher, and human.

Why are you Here?

• Teaching brought me a lot of joy and helped me to define my purpose, but for many reasons it began to feel less sustainable, and more stagnant. Throughout my 7 years of teaching, I refined my lessons, improving them time and time again to better support all learners. I refined my approach to classroom management, developing the skills to quickly build, maintain and repair relationships based on honesty and trust. I especially refined my own artistic habits, vision and craftsmanship. I eventually began to feel as though I was no longer growing. I felt like I was solvi

sertmer

Template for DTR Memo

Group Member Names:

• John Adams and Scott Ertmer

Goals and Expectations for the Project (You don't know the details of the project yet. But as you go into any project, how do YOU define success?)

• John: coming out the project feeling good about it, specifically understanding and applying the learning goals.
• Scott: ditto - big focus on growth over previous projects.

sertmer

What is your understanding of gender, gender identity, and biological sex? Is there anything more you need to learn?

• Gender is distinct from sex. It is more about the identity you have, and less about your personal biology. I think of gender as a wide spectrum with male on one end, and female on the other with a wide range of identities between. Sex is usually determined by genitalia, but also incompasses a wide range of expressions.

What was your familiarity with the history of women and software development? What surprised you about that history?

• I was unfamiliar with the history of software development in general, so this was my first intro. I usually tend to view history as being written by the victor, or at least by the most privoleged so I tend to wonder about the groups who's contributions tend to be ignored. I was not surprised to find that the history of women's contributiuons to development have been hidden or devalued. I was surprised to find that ratio of men to women was 50/50 at

sertmer

Agile & Feedback Reflection Guidelines

In interviews, you'll be asked about how you approach working in projects, and being able to describe how you utilize agile processes is a great way to help you stand out as a junior developer candidate. This reflection is meant to help you develop this skill.

With that in mind, please answer the following questions in your own gist about your group project:

1. What have you learned about the use of agile vs. waterfall in software projects?

I think of waterfall as the classic way of developing software, rigid and inflexible. It is not as modern as agile, but still has it's strengths. Waterfall is usefull when testing is infeasible, expensive, or dangerous, such as within big government projects. It also makes teams easy to stagger - when one chunk is finished, it gets passed to the next team, while the first team moves to their next chunk. However, waterfall sometimes means that project phases are quickly outdated or irrelevant to the users, since they never get to

sertmer

DTR: Define the Relationship Use this template to when conducting DTR with your project partners. It's recommended that you copy/paste this template into your own gist each time you conduct a DTR to take notes on the conversation.

Guiding Questions to Define The Relationship:

ANDREW BEN AND SCOTT

What are each of our learning goals for this project? What drives us in this project? Andrew: Writing JS intentionally.

sertmer

Template for DTR Memo ​ Group Member Names: ​Heather Faerber and Scott Ertmer

What feedback did you get on Dog Party today? What was your biggest takeaway? Heather- feedback: some minor syntax tweaks. Biggest takeaway: Get help sooner, get more comfortable with css layout. Scott- feedback: ditto with syntax and some formatting tweaks. Biggest takeaway: No time to waste. Front-load the work as much as possible. MVP: minimum viable product.

Goals and Expectations for the Project (You don't know the details of the project yet. But as you go into any project, how do YOU define success?)