Week 1:What are we doing?<br />
Got some mock-ups with Balsamiq<br />Monday: Project Kick Off<br />Hit the ground running with a planning session at the c...
Tuesday<br />By Tuesday we had a working installer from our CI builds<br />And documents in our UI!<br />Week 1<br />Week ...
Wednesday<br />That UI was crummy, let’s sketch-ize it!<br />Week 1<br />Week 2<br />Week 3<br />
Thursday<br />Documents!<br />Showed the UI to the client – we missed an important feature! Client was disappointed<br />W...
Friday<br />Changed the UI so that a record can have more than one document<br />Client was happy again!<br />Week 1<br />...
Friday<br />133t Photoshop skills led to a less sketchy UI<br />Week 1<br />Week 2<br />Week 3<br />
End of Week 1 <br />Week 1<br />Week 2<br />Week 3<br />
End of Week 1<br />Week 1<br />Week 2<br />Week 3<br />
Week 2:Let’s make it real<br />
Monday<br />Sprint planning with the client again. Got feedback from some of the stakeholders.<br />Got to try the applica...
Rest of week<br />Artem had fun building viewers for documents<br />While I got stuck with SharePoint integration!<br />We...
I love SharePoint<br />Week 1<br />Week 2<br />Week 3<br />
End of week 2<br />Week 1<br />Week 2<br />Week 3<br />
Week 3: Crunch Time<br />
Monday/Tuesday<br />By Tuesday, we could view real documents from Xstrata’s SharePoint portal – even PDF’s!<br />Week 1<br...
Monday/Tuesday<br />And even print them!<br />Week 1<br />Week 2<br />Week 3<br />
Wednesday/Thursday<br />Document searching via SharePoint<br />Week 1<br />Week 2<br />Week 3<br />
Wednesday/Thursday<br />Document searching via SharePoint<br />Week 1<br />Week 2<br />Week 3<br />
Wednesday/Thursday<br />Help!<br />Week 1<br />Week 2<br />Week 3<br />
Friday<br />Documenting<br />New requirement: web browser!<br />And a little bug fixing<br />Week 1<br />Week 2<br />Week ...
Final product<br />Week 1<br />Week 2<br />Week 3<br />
Done<br />(well nearly)<br />
3 weeks, 2 developers<br />
Communication<br />We worked from home most days<br />Visited the client office every 2-3 days<br />9AM stand-up via Skype...
Our LIB folder:<br />
Our infrastructure<br />
Mercurial was our source control<br />331 commits to source control in just 3 weeks!<br />
We have unit tests, plus 12 integration tests that cover the UI, document conversion and SharePoint!<br />
TeamCity was our low-friction CI server<br />We had a fast CI build, and a slower integration test build<br />
Our config file is beautifully small, thanks to a convention-based Autofac configuration engine:<br />
We made the latest build available to the client via HTTP<br />
AgileZen made a great remote sticky dashboard<br />
And gave us a neat burn down chart<br />
Thanks Artem, great working with you!<br />
Upcoming SlideShare
Loading in …5
×

Xstrata Kiosk Project Summary

2,269 views
2,157 views

Published on

In three weeks we built a WPF touch screen kiosk on top of SharePoint. This presentation shows how the project progressed.

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,269
On SlideShare
0
From Embeds
0
Number of Embeds
617
Actions
Shares
0
Downloads
14
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Xstrata Kiosk Project Summary

  1. 1.
  2. 2. Week 1:What are we doing?<br />
  3. 3. Got some mock-ups with Balsamiq<br />Monday: Project Kick Off<br />Hit the ground running with a planning session at the client office<br />Then spent the afternoon planning our sprints, and stubbing out our VS solution<br />Week 1<br />Week 2<br />Week 3<br />
  4. 4. Tuesday<br />By Tuesday we had a working installer from our CI builds<br />And documents in our UI!<br />Week 1<br />Week 2<br />Week 3<br />
  5. 5. Wednesday<br />That UI was crummy, let’s sketch-ize it!<br />Week 1<br />Week 2<br />Week 3<br />
  6. 6. Thursday<br />Documents!<br />Showed the UI to the client – we missed an important feature! Client was disappointed<br />Week 1<br />Week 2<br />Week 3<br />
  7. 7. Friday<br />Changed the UI so that a record can have more than one document<br />Client was happy again!<br />Week 1<br />Week 2<br />Week 3<br />
  8. 8. Friday<br />133t Photoshop skills led to a less sketchy UI<br />Week 1<br />Week 2<br />Week 3<br />
  9. 9. End of Week 1 <br />Week 1<br />Week 2<br />Week 3<br />
  10. 10. End of Week 1<br />Week 1<br />Week 2<br />Week 3<br />
  11. 11. Week 2:Let’s make it real<br />
  12. 12. Monday<br />Sprint planning with the client again. Got feedback from some of the stakeholders.<br />Got to try the application on a real touch screen!<br />Week 1<br />Week 2<br />Week 3<br />
  13. 13. Rest of week<br />Artem had fun building viewers for documents<br />While I got stuck with SharePoint integration!<br />Week 1<br />Week 2<br />Week 3<br />
  14. 14. I love SharePoint<br />Week 1<br />Week 2<br />Week 3<br />
  15. 15. End of week 2<br />Week 1<br />Week 2<br />Week 3<br />
  16. 16. Week 3: Crunch Time<br />
  17. 17. Monday/Tuesday<br />By Tuesday, we could view real documents from Xstrata’s SharePoint portal – even PDF’s!<br />Week 1<br />Week 2<br />Week 3<br />
  18. 18. Monday/Tuesday<br />And even print them!<br />Week 1<br />Week 2<br />Week 3<br />
  19. 19. Wednesday/Thursday<br />Document searching via SharePoint<br />Week 1<br />Week 2<br />Week 3<br />
  20. 20. Wednesday/Thursday<br />Document searching via SharePoint<br />Week 1<br />Week 2<br />Week 3<br />
  21. 21. Wednesday/Thursday<br />Help!<br />Week 1<br />Week 2<br />Week 3<br />
  22. 22. Friday<br />Documenting<br />New requirement: web browser!<br />And a little bug fixing<br />Week 1<br />Week 2<br />Week 3<br />
  23. 23. Final product<br />Week 1<br />Week 2<br />Week 3<br />
  24. 24. Done<br />(well nearly)<br />
  25. 25. 3 weeks, 2 developers<br />
  26. 26. Communication<br />We worked from home most days<br />Visited the client office every 2-3 days<br />9AM stand-up via Skype<br />Chatted via Skype during the day<br />
  27. 27. Our LIB folder:<br />
  28. 28. Our infrastructure<br />
  29. 29. Mercurial was our source control<br />331 commits to source control in just 3 weeks!<br />
  30. 30. We have unit tests, plus 12 integration tests that cover the UI, document conversion and SharePoint!<br />
  31. 31. TeamCity was our low-friction CI server<br />We had a fast CI build, and a slower integration test build<br />
  32. 32. Our config file is beautifully small, thanks to a convention-based Autofac configuration engine:<br />
  33. 33. We made the latest build available to the client via HTTP<br />
  34. 34. AgileZen made a great remote sticky dashboard<br />
  35. 35. And gave us a neat burn down chart<br />
  36. 36. Thanks Artem, great working with you!<br />

×