Your SlideShare is downloading. ×
ForceManager production   20121231-ss
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Saving this for later?

Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime - even offline.

Text the download link to your phone

Standard text messaging rates apply

ForceManager production 20121231-ss

643
views

Published on

2013 Development Process definition. Based on User Agile Development & SCRUMBAN.

2013 Development Process definition. Based on User Agile Development & SCRUMBAN.

Published in: Technology

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
643
On Slideshare
0
From Embeds
0
Number of Embeds
18
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. The product method Product chain
  • 2. Index – ForceManager Product Method 3
  • 3. Index – ForceManager Product Method 1. User Research Interviews 2. Validated Designs SPRINT 1 3. Estimate 4. Feature Scope 5. Investments SPRINT 2 6. Development 7. Quality Assurance Revision 8. Release SPRINT 3 4
  • 4. 1. User Research Interviews SPRINT 1 Responsibility • Get from the Stakeholders the feature requirements Participants • StakeHolders • Product Owner[s] • UX/UD Team Member[s] Output • Feature requirements 5
  • 5. 2. Validated Designs SPRINT 1 Responsibility • Generate wireframes/prototypes following the stakeholders requirements • Generate specifications following the stakeholders requirements Participants • StakeHolders • UX/UD Team Member[s] • Product Owner[s] Output • Feature wireframes or prototype • Feature specifications 6
  • 6. 3. Estimations SPRINT 1 Responsibility • Development team evaluation related to the feature specifications Participants • Product Owner[s] • UX/UD Team Member[s] • Development Team Member[s] • Quality Assurance Members[s] • Infraestructure Team Members[s] Output • Feature estimations • Feature Risk • Investment Plan • Quality Assurance Plan 7
  • 7. 4. Feature scope / versioning SPRINT 1 Responsibility • Define the scope of the feature for all the versions Participants • StakeHolders • Product Owner[s] Output • Feature roadmap • Development calendar 8
  • 8. 5. Investments SPRINT 2 Responsibility • Execute the investments included on the investment plan • Iterate the estimations Participants • Product Owner[s] • Development Team Member[s] • Infraestructure Team Members[s] Output • Estimations • Development calendar 9
  • 9. 6. Development SPRINT 2 Responsibility • Develop the feature according to the scope specifications and designs • Release a tested code • Log the work progress Participants • Development Team Member[s] • UX/UD Team Member[s] • Infraestructure Team Members[s] UNIT TESTING Output • Feature tested (*) to be certified INTEGRATION TESTING • Log of work ACCEPTANCE TESTING 10
  • 10. 7. Quality Assurance Revision [1] SPRINT 3 Responsibility • Exploratory Testing over the product front-ends • Generate Bug/Improvements for the development Team Participants • Product Owner[s] • Quality Assurance Member[s] Output UNIT TESTING • Product[s] plan execution result • Kanban Tickets INTEGRATION TESTING ACCEPTANCE TESTING 11
  • 11. 7. Quality Assurance Revision [2] SPRINT 3 Responsibility • [Web, Server] Deploy the product on pre-production environment • [Mobile] Release a release candidate and test with real customers • Check the compliance of the product Participants • Product Owner[s] • Quality Assurance Member[s] • Infraestructure Team Members[s] UNIT TESTING Output • Product approved INTEGRATION TESTING ACCEPTANCE TESTING 12
  • 12. 8. Release SPRINT 3 Responsibility • Release a tested and stable product to PRODUCTION Participants • Product Owner[s] • Infraestructure Team Members[s] Output • Product released 13
  • 13. SCRUMBANThe team method
  • 14. Team Responsibilities Product Manager Product Owner Scrum Team Members Force SPRINT • User Experience Experts Manager Backlog • Quality Assurance Experts • Developers / Engineers Product Backlog KANBAN Backlog Scrum Master • Agility “Guardian” • Team leader 15
  • 15. Team members responsibilities Product Owner • Stakeholders agent in front the development team. Every requirement must be channel through him • He must keep the product backlog and prioritize and decide which tasks will be included in the Sprint backlog or as a Kanban ticket • Finally must revise the output products with the Stakeholders (sometimes himself if the product owner is the product manager) UX/UD Team • UX / UI Expert who manage the prototyping, wire-framing getting the users requirements and expectations • Provides to the development team the UI checked with the customer/stakeholders 16
  • 16. Team members responsibilities QA Team • Define Quality Plans • Product Quality Responsibility • Block / Authorize the release of the product versions Development Team • They’ve the responsibility to deliver the product output planned for every SPRINT, updating the Backlog status and, in general, following the organization quality and process guidelines • StandUp meeting • Log of Work • Integration and Unit testing • Code documentation 17
  • 17. Team members responsibilities SCRUM Master • Developer Engineer who implies the rest of the team to follow the guidelines have been agreed by the organization • SM check the following of the team guidelines • Ensures the team is fully productive (Remove Barriers…) • Ensures the team follow the process (Version Control Policy, Log Of Work, ALM flow…) • Manage the state of the Cardwall and the daily StandUp • Report to the Product Owner the progress of the SPRINT • Include new guidelines could improve the team behavior Our organization will not have any specific SM, all of us will be the SM in at least on of the sprints of the YEAR. 18
  • 18. Development Team Insights/KPI For every SPRINT we will store the next KPI : • % Capacity Reported: Log Work / Total Work Capacity • % Achievements: Closed Work / Total Plan Capacity • Velocity: Closed Work (hours) • % StandUp Meetings: #StandUp / #DaysInSprint Is the responsibility of the Scrum Master to work to maintain good results for this insights and report them to the product owner at the end of the SPRINT. 19
  • 19. ¡Thank you!ForceManager Team