Software Development Lifecycles
- 1. Software Development Lifecycles SDLCs, Github, Pivotal, and FUN
- 2. Excitement begins now ● Types of SDLCs ● Typical workflows ● Github demo ● Pivotal demo ● Get pumped
- 3. Aww yeahh, let’s roll! ● Requirement gathering ● Planning ● Building ● Testing ● Deploying ● Maintaining
- 4. Aww yeahh, let’s keep rolling? ● Requirement gathering ● Planning ● Building ● Testing ● Deploying ● Maintaining (lol just kidding, start over)
- 5. “Even the best planning is not so omniscient as to get it right the first time.” Fred Brooks
- 6. Apparently we’re rolling forever (OODA Loop)
- 7. Gotta roll fast ● “Agile” software methodologies ● Not really a thing you do, it’s a thing you are ● Software is iterative, so... ● The full waterfall cycle is shortened into an iteration ● Kept intentionally short so we can adjust course as needed
- 10. Iteration Planning Meeting (IPM) ● Kicks off a sprint ● Break down remaining work into “tickets” ● Estimate a ticket’s “points” of effort ● Fill sprint backlog based on team velocity
- 11. Scrum / Stand ● Daily meeting (usually morning) to put team on same page ● Usually severely timeboxed ● Work done, work to do, any blockers ● Anything else goes to a “parking lot” ● Helps to eliminate distractions later by identifying roles early
- 12. Tickets
- 13. Retrospective ● Review the previous iteration’s work ● What was completed, what was not ● Present work to stakeholders (demo) ● What worked well, what did not
- 14. Example Ticket ● Estimated and assigned to backlog ● Started (pivotal), branch created off of master (github) ● Dev work done, committed (github) ● Pushed to staging server, marked as finished (pivotal) ● Tested by PM and/or QA on staging, marked as delivered or rejected (pivotal) ● Pull request / code review submitted (github) ● Demo’d at IPM, marked as accepted/rejected (pivotal)
- 15. Github + Pivotal Demo Get pumped for source control and ticket management