Scrum Hell or Highwater

295 views

Published on

Do you want to deliver better products and services to a more satisfied client base? Do you think adopting an agile team strategy is the way to achieve those goals? Well buckle up, Dixie cup, and let us explain exactly how your efforts are about to go awry. Jennifer Chance has spent the past year bringing the agile development model known as “Scrum” to The McCombs School of Business at The University of Texas. She’ll be the first to tell you that it hasn’t been easy. Mistakes and failures are opportunities to learn, though, and those opportunities are even more appealing if you’re not the one doing the failing. Whether you are considering Scrum, another agile initiative, or none at all, Jen’s no-nonsense approach to a better workflow offers simple, useful solutions for scenarios all of us are likely to encounter. Come and see what you and your team can learn from someone else’s bumpy, blustery journey to become agile--come hell or high water.

Published in: Education
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
295
On SlideShare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
7
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Clyde Commons

    Describe everyone
  • Agile project management is a style where you complete small portions of a deliverable in short cycles

    Scrum is the most popular style of agile – it focuses on being highly flexible and recognizing that your client will often need to make changes to the original idea of what the deliverable is supposed to be, as they learn more about what you’re creating.
  • The Team is everybody that’s on that first slide. It’s my magnificent seven. These are the guys that are going to be doing the work.

    Product owner – this is the person who wants the work done. They are the one who should get across the vision to the team. In this case it’s a marketing director of a program in our school, the MSTC program.

    Scrum Master – is the person who facilitates the work getting done. They’re the person when someone on the team is having a problem – they remove that obstacle. They are there to help the product owner as well. Though the scrum master seems like a manager, it’s different. Their main job is to listen to the needs of all involved and make sure they are met, while keeping the team is following scrum practices. We want the team to be working as close to full speed as possible.
  • Sent to class – small investment – confidence – new skill set
  • It saves everyone time – don’t have to sit around and talk about how it could work.
  • With that confidence

    Table cloth out from underneath
  • One of the things we wanted - and our clients wanted, for the first time ever was a site light in content
    One of the things the did was more of editing content down – he completed that quickly
    I knew he would have more downtown – we had to focus on this one project

    Usually I would start him on another writing project right away, but because our developers and our designers were so swamped – I started giving Jon more technical jobs.
    Deeper understanding of HTML/ our CMS

    At first jon didn’t like it but then


  • #2Know how this project should go and tell them how it should go.
    Tell them this is what we do, this is how we work – and have them agree to it.
    [when you go to a scuba class –it’s not – we could do it x or y ] this is how we approached our client and it worked out really well
    We tried to get everyone in on it before and it sucked

  • Thank you guys – don’t forget about that hamburger
    Clyde Commons
  • Scrum Hell or Highwater

    1. 1. Who We Are
    2. 2. What Is Scrum?
    3. 3. • Product Owner • The Team • Scrum Master
    4. 4. Mistake #1 Assigning the scrum master role to the wrong person
    5. 5. Agile Tip #1 Choose a less productive team member to be your SCRUM master.
    6. 6. This is Mark.
    7. 7. Mark was stuck.
    8. 8. Benefits of choosing a less productive team member to be your scrum master: 1. Invigorate a complacent employee 2. No loss of productivity 3. Gain insight on how to fail productively
    9. 9. Mistake #2 Collaborating with client on how the project will proceed
    10. 10. Agile Tip #2 Give your client zero options (at least at first)
    11. 11. This is Brandi.
    12. 12. Brandi would meet with us every morning in person Brandi’s bosses would give Brandi the authority to represent their interests in these meetings Brandi is responsible for informing her bosses of what is said in meetings Any changes to already approved items would add length to the approved timeline
    13. 13. Benefits of giving your client zero options: 1. Establish best practices early 2. Plan your project how YOU want it to proceed 3. Gives client realistic expectations on a feasible timeline
    14. 14. Mistake #3 Allowing team members to do what they do best
    15. 15. Agile Tip #3 Assign your team members small jobs they aren’t used to.
    16. 16. This is Jon
    17. 17. Benefits of giving team members small jobs they suck at: 1. Gives individual team members a better understanding of their peers’ responsibilities 2. More hands on deck during crunch times 3. Gives individual team members a better, more versatile resumé
    18. 18. Agile Tip #1 Choose a less productive team member to be your SCRUM master. Agile Tip #2 Give your client zero options (at least at first) Agile Tip #3 Assign your team members small jobs they aren’t used to.

    ×