Who is ProDataMan?

ProDataMan, Professional Data Management, is an Information Technology Consulting and Knowledge Transfer firm. ​Professional Data Management specializes in Data Driven applications based on SQL Server, .Net and SharePoint. Using the latest techniques and technologies ProDataMan efficiently develops solutions directly addressing customers pain points. But what good is a ground breaking solution if no one knows how to use it? This is why our consultants are not JUST geeks! OK well maybe a few of them, but for the most part our consultants are also Trainers and/or Artists with actual people skills!! How's that for a change of pace. So when the project is complete one of our highly experienced and certified consultant / trainers can present to your entire team Tips, Tricks and Best Practices for making the most of the new solution.

DevOps Transformations

Brain dump on DevOps for Executives, Directors and Team Leads planning to implement DevOps within their organizations. ​Plug into the Matrix and dive into this experience of drinking from the DevOps firehose. When you unplug from the DevOps Matrix you will not know Kung-Fu but you will be up to speed on all things DevOps from Agile Development and Test Driven Development to Continuous Integrations, Continuous Delivery and Continuous Deployment because this workshop touches on everything.

Learn more »


People, Technology, Business Systems As your organization embarks on the road to change in the 21st century, Professional Data Management can help define, design, build, implement, and manage enterprise level business solutions. How do we deliver value to the client? Through understanding the upfront business processes, the long term goals, and delivering a solution that leverages the full power of Microsoft .NET Technologies to bring added value to the organization. From developing N-Tier Applications, to Information Security, to Enterprise Integration, Professional Data Management helps lower the Total Cost of Ownership (TCO) and maximize the return on IT investment. We build solutions that are reliable, scalable, and secure using a framework developed from years of experience. The result: on time, on budget, wins to the client.

Learn more »

Workshops and Courses

On-Site Workshops run for 3 days 8 hours per day, On-Line Workshops run for 4 days 5 hours per day with offline reading and video content. Online workshops follow our unique Choose Your Own Adventure style Presentation Approach allowing attendees to choose platform, tool and programming / scripting languages in which to see demos and do hands-on exercises.

Learn more »

5 Agile Rules

Antoine Victor 11/19/2019 9:32:17 PM

Sprint Planning: The 60/40 Split
2-4 hours of Sprint planning for each week of a Sprint should yield 60% of delivery team tasks necessary to complete a user story defined and documented prior to the Sprint
The 80/20 Commitment
The average agile team incurs 10-30% technical debt in each Sprint. Mature teams closer to 10% newer Agile teams closer to 30%. Commit the team to 80% instead of 100% of their capacity leaving 20% spare team capacity to pay down technical debt furring the sprint
The 20% Planning Cushion
Whatever your team’s commitment in a Sprint plan 20% over that commitment in case you work more efficiently than expected. For example if your team’s Velocity is 100 story points per Sprint and you follow the 80/20 Rule committing to only 80% of capacity you Sprint commitment would be 80 story points therefore you should plan to the task level 100 story points or 120% of your Sprint commitment. That way if you finish all stories or a story is blocked before the end of the Sprint there are additional stories with detailed plans already available to pull into the sprint backlog
The 20/20 Epic Check
If a user story has more than 20 acceptance criteria statements (written in gherkin format) or it has more than 20 delivery team tasks than it’s probably am Epic masquerading as a user story. An Epic is to large and complex to be completed in a single Sprint and should be broken down and into multiple smaller user stories
Lighting brings the team together
In order to get good cross-functional team input we should invite all even loosely related team members to our Agile Planning meetings.  The problem tends to be that those team members do not want to sit around for hours listening to developers and testers talk about User Stories that are not relevant to their job role or assigned tasks. A “Lightning Round of Planning Poker can solve this problem.  In the Lightning Round we spend no more than 3 minutes on each User Story just validating the Product Owners original story point estimation for the story and that the Accept Criteria is sufficient to build good tests and most importantly to get input from all parties that will interact with the modules before deployment.  Spending 3 minutes or less on each story ensures that each story will be discussed briefly usually within the first 30 minutes of the meeting.  That means that the loosely related teams members get a brief overview of all stories to be completed in the coming sprint as well as give their input about the stories that require their input.
Bonus Rule:
The Rule of Focus (AKA the 3/15/60 Rule)

The average information worker is int interrupted or switches tasks every 3 minutes. Once interrupted it can take anywhere from 15 minutes to an hour to regain optimal levels of productivity.

Made my flight with minutes to spare!  Road Warrior!!

Publishing from the plane at the gate