Today had more string templates and more MVC pattern in Java. Lots of little details to meet sometimes volatile acceptance criteria.
An after hours project led to me teaching some basic computer skills today, and it was very rewarding and also taught me some things about teaching- namely, that doing it once is great for an introduction but won't work for skill retention. Always give the student opportunities to ask questions, because what they ask will teach you how to teach them.
DevOps is an important part of everything that we do, and I think that these articles are a good introduction to a little bit of the why and how.
A showcase is an interesting beast, and the style of it depends heavily on your audience. Technical, nontechnical, big picture, speedy, audience-driven, drawing out the audience...
Big displays on walls made out of post-its and notecards are very valuable, and there are many types of them. An iteration priority overview has a "priority line" and every time a client wants to add something to the "must do now, this iteration, today" pile, they have to take a card and put it below the priority line (which represents what will happen during this next stage of the project). As I understand it, this helps the client understand that the resources are limited and that scope creep cannot all be fulfilled in the original time period...
An after hours project led to me teaching some basic computer skills today, and it was very rewarding and also taught me some things about teaching- namely, that doing it once is great for an introduction but won't work for skill retention. Always give the student opportunities to ask questions, because what they ask will teach you how to teach them.
DevOps is an important part of everything that we do, and I think that these articles are a good introduction to a little bit of the why and how.
A showcase is an interesting beast, and the style of it depends heavily on your audience. Technical, nontechnical, big picture, speedy, audience-driven, drawing out the audience...
Big displays on walls made out of post-its and notecards are very valuable, and there are many types of them. An iteration priority overview has a "priority line" and every time a client wants to add something to the "must do now, this iteration, today" pile, they have to take a card and put it below the priority line (which represents what will happen during this next stage of the project). As I understand it, this helps the client understand that the resources are limited and that scope creep cannot all be fulfilled in the original time period...