Hackpads are smart collaborative documents. .


892 days ago
Unfiled. Edited by jhibbets@gmail.com , Ashley McClelland , Anita Cafiero 892 days ago
jhibbets@gmail.com Agile development 101
Jen Krieger
A little bit of history, background about waterfall methodology
Care about working software, not intense documentation describing how the software should work
Roles: Project manager, engeringing/developer, QE/engineering, architect
Project manager --> scrum masters | self-organizaiton teams
What does a scrum workflow look like?
1) Backlog (lots of items aka stories) - a product owner grooms the backlog
2) Sprint planning (time frame, perhaps 2-4 weeks) - takes a certain number of items from the backlog [recommend 2 week intervals]. Goal of this meeting is to figure out what the team will work on for the next 2 weeks/iteration 
3) team goes an iteration; everyday teams go through a stand-up meeting
4) At the end of the iteration, the team does a demo; 
Ashley M 5) Retrospective ("retro") - the final meeting at the end of the iteration when the team meets to talk about what went well, what didn't go well, what to do different next time. 
jhibbets@gmail.com Cycle repeats as a mini waterfall: Design, Develop, QE, Release
Using Trello as a scrum tool (even though it's a kanban tool). Waffle.io can also be used.
Agile != scrum
Core practices for Kanban:
  • Visualize
  • Limit work in progress
  • Manage flow
  • Make policies explicit
  • Implement feedback loops
  • Improve collaboratively, evolve experimentally
Todo | Doing | Done
WIP == Work in progress
Start-finishing | Stop-starting == start finishing and don't start too much
Kanban is a pull system; team members will pull next tasks from the to-do column
"How to split a user story" [via agile for all] 
jhibbets@gmail.com Epic -> Feature -> User story
Anita C Cool things: 
No more bookmarks in your browser!
Script to run in Trello - agile sprint scripting
892 days ago
Unfiled. Edited by Anita Cafiero , jhibbets@gmail.com 892 days ago
Anita C Waffle.io
Project management solution for GitHub issues. Provides a UI layer to Issues.
Basic column list
Backlog: firehose of all tasks to complete on project
Ready: move tasks here when ready to assign to sprint
In progress: actively working on (one or two per person for max efficiency)
Complete: issues moved to "complete" will be closed and cleared every 7 days. Change this if you don't want to lose track
Multiple repositories can be added to one Waffle.io board
Moving issues:
git commit -am "closes #2"  (keywords to close the issue: closes, fixes, resolves) 
push to master closes the issue
If creating new branch with push:
git push origin HEAD:[issue branch]
Merging pull requests will close the issue on Waffle if issue number is in the Pull Request title field. (closes #1, for example)
jhibbets@gmail.com Open source teams will use labels on waffle boards; help wanted or low hanging fruit are great ways to attract new contributors
Blue banner at the bottom to create project needs to be selected in order to start
Project settings --> change columns and settings for each one

Contact Support

Please check out our How-to Guide and FAQ first to see if your question is already answered! :)

If you have a feature request, please add it to this pad. Thanks!

Log in