Agile Product Development Team
- A ‘Product Owner’ who is best described as:
- A software savvy business analyst who is intimately aware of the business domain
- A staunch advocate of the customer’s needs while remaining adept at conveying conflicts when the customer’s needs do not coincide with the development effort.
- A liaison between the customer and the company and they are the sole exterior filter between the team and all outside entities.
- For the Agile Scrum Master it is all about mastering time. It begins with the shortest duration meeting, the daily scrum, which often manifests itself in a daily ‘stand-up’ meeting.
- The stand-up, should be limited to 15 minutes in which each team member is given a slice of that time to express their
- Progress from the day before
- What is on their plate for that day
- And any impediments
- The scrum master may at this time coordinate help or take the concern off-line, always mindful of the time slice.
- All other meetings are facilitated by the scrum master whose goals has two goals:
- Maintain the time-box
- A time-box is the strongly held duration of every meeting. A one hour meeting must be over in no more than 60 minutes.
- A time-box is the strongly held duration of every meeting. A one hour meeting must be over in no more than 60 minutes.
- Make sure no follow-ups fall through the cracks.
- Maintain the time-box
- Agile is about delivering iterations of value on time. The emphasis is on time. Product features remain backlogged in order to meet the iterations delivery.
- The scrum master coordinates other meetings that include use case development and estimation poker which help to plan the functionality the iteration
- The stand-up, should be limited to 15 minutes in which each team member is given a slice of that time to express their
- The Programmer reviews the technical specifications, discusses the intent of functional specification and use cases with the product owner and tester and incrementally develops the functionality. Upon completing the unit test of the functionality the tester is asked to comment.
- Testers evaluates whether the functionality fulfills the validations. A list of validations are created at the start of each iteration, that when met, will indicate completion of that functionality. Before the iteration is delivered the tester plays the key role of performing system testing designed to make certain there are no regression errors. Regression errors are second only to a failed unit test
Influences on the Agile Team
- Director of Project Development is responsible for or may delegate:
- Responding to Requests for Proposals (RFPs)
- Performing product demonstrations
- Drafting specifications
- The directory works with each Product Owner to establish each team’s composition, while assessing the talents of each team member and pairing that with the complexity of the functionality backlog they are given.
